[scripts] Persist ur_function_t max ID in registry generation #20284
Conversation
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
kswiecicki
approved these changes
Oct 6, 2025
KFilipek
force-pushed
the
id_generation_fix
branch
from
9038945 to
d907c3f
Compare
Contributor
Author
|
@intel/llvm-gatekeepers all checks passed, please merge |
kswiecicki
approved these changes
Oct 7, 2025
Contributor
|
@intel/llvm-gatekeepers please consider merging |
Contributor
Author
|
Hi all @intel/llvm-gatekeepers, if it's okay please merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Read the stored max function ID from registry.yml and treat it as the bound for new IDs.
This approach avoids reusing freed ID's from legacy functions.