KhronosGroup / KhronosGroup/SPIRV-Cross

Component decoration support

Open
#1,428 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
GLSL
Stars
2.5k
Forks
713
Avg merge
2d 18h
Merged PRs (30d)
16

Description

Is it hard to implement I/O component decoration emulation for glsl that don't support it.

```
layout(location = 0, component = 0) in vec2 uv1;
layout(location = 0, component = 2) in vec2 uv2;
```

->

```
in vec4 stage_input_location_0;

// uv1 = stage_input_location_0.xy
// uv2 = stage_input_location_0.zw
```

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start from the GLSL examples in the issue and trace how SPIR-V component decorations are translated for GLSL inputs. Done means inputs at location 0 with components 0 and 2 are emulated through one vec4 stage input, with the corresponding component values exposed as shown.

Written by the indexing model from the issue text.

Assessment

Domain
compilers, computer-graphics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.