Document ILC generic analysis #123566
Open
Document ILC generic analysis #123566
+58
−0
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
github-actions
bot
added
the
needs-area-label
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request adds comprehensive documentation about how ILC (IL Compiler) handles generic types and methods in NativeAOT compilation. The documentation is based on learnings from PR #122012, which dealt with tracking concrete dependencies of open generic methods.
Changes:
- Adds a new "Compiling generics" section to the ILC architecture documentation covering shared generics, canonicalization, runtime-determined types, generic dictionaries, generic virtual methods (GVMs), and shadow method nodes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I tried to write down some of what I learned (with much help from @MichalStrehovsky) while working on #122012 in a way that might be helpful to others learning about ILC in the future.