Align methods at 16-byte boundaries for CFG #106132
Merged
Conversation
This file contains 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
Fixes dotnet#105326 Per https://learn.microsoft.com/en-us/windows/win32/secbp/pe-metadata#function-alignment "Functions that are address taken and are therefore included in the GFIDS table should be made 16-byte aligned, if possible.". We'd align at 4 bytes if SIZE_OPT is enabled.
jkotas
approved these changes
Aug 8, 2024
|
/ba-g nuget restore issue in an unrelated leg |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #105326
Per https://learn.microsoft.com/en-us/windows/win32/secbp/pe-metadata#function-alignment "Functions that are address taken and are therefore included in the GFIDS table should be made 16-byte aligned, if possible.". We'd align at 4 bytes if SIZE_OPT is enabled.
Cc @dotnet/ilc-contrib