gen-fields: use explicit legacy field source#127
Merged
Conversation
Signed-off-by: Nick Curry <ncurry@nvidia.com>
nccurry
force-pushed
the
ncurry/legacy-field-source
branch
from
e2bd544 to
ad55ab1
Compare
rvatkar
reviewed
May 29, 2026
Signed-off-by: Nick Curry <ncurry@nvidia.com>
Signed-off-by: Nick Curry <ncurry@nvidia.com>
Signed-off-by: Nick Curry <ncurry@nvidia.com>
rvatkar
approved these changes
Jun 22, 2026
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
2 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.
Summary
Motivation
This separates curated compatibility names from generated header-derived aliases. The generator no longer has to infer the curated lowercase names from generated output or header/comment patterns; they now live in an explicit source file that can be reviewed directly.
Testing