KhronosGroup / KhronosGroup/glslang

Check for reuse of binding numbers.

Open
#926 1 comment 0 reactions 0 assignees View on GitHub
GLSL/ESSL Missing Functionality
Dominant language
C++
Stars
3.6k
Forks
989
Avg merge
1d 2h
Merged PRs (30d)
31

Description

From the latest 4.5 specification:

> It is a compile-time or link-time error to use the same binding number for more than one image or more
than one sampler. It is a compile-time or link-time error to use the same binding number for more than one atomic counter, unless the offset for the atomic counters sharing the same binding are all different.

This still needs to be implemented.

Contributor guide

Open the contributing guide

Research direction

Start by reading the quoted GLSL 4.5 specification rule and locating the compiler validation responsible for resource binding numbers. Check how images, samplers, and atomic counters are represented and validated, then add coverage for duplicate bindings and confirm the specified exceptions are enforced.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers
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.