-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HLSL] Implement Root Signature Lexer for Descriptor Tables #126563
Comments
@llvm/issue-subscribers-clang-frontend Author: Finn Plummer (inbelic)
This issue handles the lexing of a root signature string into a token representation of the data. Specifically, it handles and defines all the tokens required for a Descriptor Table and its clauses.
For the sake of scope, we will let the lexing of floating literals be deferred until needed for Static Samplers. Other than that this pr should allow us to simply define new enumerations/keywords in AC:
|
For the sake of scope, we will let the lexing of floating literals be deferred until needed for Static Samplers. Other than that this pr should allow us to simply define new enumerations/keywords in `RootSignatureTokenKinds.def` for when they are used in the parser. We could have defined all of these keywords here, but for the sake of correctness in review we will let them be split up. - Define `RootSignatureLexer` and provide a public `LexToken` method for external use - Define the file `RootSignatureTokenKinds` to define required tokens and allow for future custom keywords/enums - Implement the internal methods required to parse the different types of tokens (integers, flag enums, puncuators...) - Add test harness for unit testing and the respective unit tests for lexing the tokens Resolves llvm#126563 --------- Co-authored-by: Chris B <[email protected]>
For the sake of scope, we will let the lexing of floating literals be deferred until needed for Static Samplers. Other than that this pr should allow us to simply define new enumerations/keywords in `RootSignatureTokenKinds.def` for when they are used in the parser. We could have defined all of these keywords here, but for the sake of correctness in review we will let them be split up. - Define `RootSignatureLexer` and provide a public `LexToken` method for external use - Define the file `RootSignatureTokenKinds` to define required tokens and allow for future custom keywords/enums - Implement the internal methods required to parse the different types of tokens (integers, flag enums, puncuators...) - Add test harness for unit testing and the respective unit tests for lexing the tokens Resolves llvm#126563 --------- Co-authored-by: Chris B <[email protected]>
This issue handles the lexing of a root signature string into a token representation of the data. Specifically, it handles and defines all the tokens required for a Descriptor Table and its clauses.
For the sake of scope, we will let the lexing of floating literals be deferred until needed for Static Samplers. Other than that this pr should allow us to simply define new enumerations/keywords in
RootSignatureTokenKinds.def
for when they are used in the parser. We could have define all of these keywords here, but for the sake of correctness in review we will let them be split up.AC:
RootSignatureLexer
and provide a publicLexToken
method for external useRootSignatureTokenKinds
to define required tokens and allow for future custom keywords/enumsThe text was updated successfully, but these errors were encountered: