Separate frozen object owning type from allocation site#129113
Merged
Conversation
Fixes dotnet#129074. Type names ending with numbers could clash with the callsite ID.
Contributor
|
Tagging subscribers to this area: @agocke, @dotnet/ilc-contrib |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts NativeAOT/ILC frozen object symbol name mangling to prevent collisions between an owning type name that ends in digits and the appended allocation-site ID.
Changes:
- Insert a delimiter (
'_') between the owning type’s mangled name and the allocation-site ID inSerializedFrozenObjectNode.AppendMangledName.
jkotas
approved these changes
Jun 8, 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
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.
Fixes #129074.
Type names ending with numbers could clash with the callsite ID.