-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[wasm] Fix perf pipeline builds #72234
Conversation
/azp run runtime-wasm |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsPerf pipeline builds broke recently as detailed in #72104, and #72105 . AOT builds broke because il-linking would result in 10 assemblies, instead of 145! This was because the default is
|
Azure Pipelines successfully started running 1 pipeline(s). |
.. `TrimMode=link`. The `TrimMode` values changed in dotnet/sdk#26246 .
c7cfad0
to
c6a97fa
Compare
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
I don't think we should make partial the default, the only thing breaking in this case is the perf pipeline and making more aggressive trimming is the right default for wasm outside of blazor |
I'm testing |
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.
I'll approve this to unblock the perf lane immediately but we need to resolve the new modes properly
Perf pipeline builds broke recently as detailed in #72104, and #72105 . AOT builds broke because il-linking would result in 10 assemblies, instead of 145! This was because the default is
TrimMode=full
now.TrimMode=
partialto opt-in to the older
linkbehavior
.TrimMode
values changed in Change linker to trim everything by default in 7.0 sdk#26246 .Note: This restores the old behavior. But we want to eventually enable
TrimMode=full
.Fixes #72104
Fixes #72105