-
Notifications
You must be signed in to change notification settings - Fork 566
Move FixLegacyResourceDesignerStep to post-trim pipeline #11059
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
70f7f30
[illink] Move FixLegacyResourceDesignerStep to post-trim pipeline
sbomer 77de75d
[targets] Fix NativeAOT designer assembly trimming
sbomer e9edefd
Merge remote-tracking branch 'origin/main' into fix-resource-designer
sbomer f0059fd
Fix merge conflict: remove FixAbstractMethodsStep from ILLink csproj
sbomer 64d4ed1
Root designer assembly to prevent ILLink from trimming resource prope…
sbomer 924649e
Use TrimmerRootDescriptor instead of TrimmerRootAssembly for designer…
sbomer 8be3817
Update SkiaSharp test to expect XA8000 instead of IL8000 for release …
sbomer f12d747
Merge remote-tracking branch 'origin/main' into fix-resource-designer
sbomer 83a8f64
Fix incremental build: use WriteOnlyWhenDifferent for linker descriptor
sbomer 6e870ef
Add TODO to simplify TrimmerRootDescriptor once dotnet/runtime#126518…
sbomer a92e39f
Fix SkiaSharp NativeAOT test to expect XA8000 build failure
sbomer 4691223
Merge remote-tracking branch 'origin/main' into fix-resource-designer
sbomer 1eec909
Update APK size reference baselines
sbomer 196e393
Update PostTrimmingPipeline summary to mention FixLegacyResourceDesig…
sbomer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤖⚠️ Performance — The
preserve="all"descriptor prevents ILLink from trimming unused resource properties in the designer assembly. In the old ILLink custom step flow,FixLegacyResourceDesignerStepran beforeMarkStep, so ILLink could track which designer properties were actually referenced and trim the rest. With the post-trim approach, all properties must survive ILLink intact.The
BuildReleaseArm64XFormsDotNet.MonoVM.apkdescshows the designer assembly growing from ~19 KB to ~258 KB (~13× increase). For the simple app it's negligible (+400 bytes), but resource-heavy apps will see a larger impact.The TODO references dotnet/runtime
#126518for switching toTrimmerRootAssembly. However, the_FixRootAssemblytarget upgrades allTrimmerRootAssemblyentries toRootMode="All", so switching wouldn't reduce the preserved surface — it would just simplify the MSBuild XML. Is the size regression considered acceptable for the architectural benefits of removing the ILLink step, or is there a plan to recover trimming of unused designer properties later?Rule: Don't remove caches without measurement (Postmortem
#57)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is accurate, and by design per #11059 (comment).