Introduce program linkage#295
Merged
Merged
Conversation
The C++ specification talks in terms of module, external, internal, and no linkage. These linkages in C++ refer to translation units. For HLSL, we have some differences in how programs are built and linked that can't be fully expressed in that language. Specifically, we have a notion of a program-export (entry functions, export keyword), that denotes a linkage that is more external than just cross translation unit. This change introduces a term _program linkage_ to refer to names that have linkage outside a linked or freestanding program.
hekota
added a commit
to hekota/llvm-project
that referenced
this pull request
Aug 7, 2024
…e sure only shader entry points and exported functions are visible from the module (have program linkage). Linkage of all other functions will be changed to internal. Related spec update: microsoft/hlsl-specs#295
bharadwajy
reviewed
Aug 8, 2024
hekota
added a commit
to llvm/llvm-project
that referenced
this pull request
Aug 16, 2024
An HLSL function has internal linkage by default unless it is: 1. shader entry point function 2. marked with the `export` keyword (#92812) 3. patch constant function (not implemented yet) This PR adds a link-time pass `DXILFinalizeLinkage` that updates the linkage of functions to make sure only shader entry points and exported functions are visible from the module (have _program linkage_). All other functions will be updated to have internal linkage. Related spec update: microsoft/hlsl-specs#295 Fixes ##92071
llvm-beanz
added a commit
to llvm-beanz/hlsl-specs
that referenced
this pull request
Feb 9, 2025
The C++ specification talks in terms of module, external, internal, and no linkage. These linkages in C++ refer to translation units. For HLSL, we have some differences in how programs are built and linked that can't be fully expressed in that language. Specifically, we have a notion of a program-export (entry functions, export keyword), that denotes a linkage that is more external than just cross translation unit. This change introduces a term _program linkage_ to refer to names that have linkage outside a linked or freestanding program.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The C++ specification talks in terms of module, external, internal, and no linkage. These linkages in C++ refer to translation units. For HLSL, we have some differences in how programs are built and linked that can't be fully expressed in that language.
Specifically, we have a notion of a program-export (entry functions, export keyword), that denotes a linkage that is more external than just cross translation unit.
This change introduces a term program linkage to refer to names that have linkage outside a linked or freestanding program.