-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Do we still need [AggressiveOptimization] on so many methods? #71261
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue Detailsdotnet/coreclr#22191 added a bunch of [AggressiveOptimization] attributes to methods throughout SpanHelpers and elsewhere that make heavy use of intrinsics, e.g. runtime/src/libraries/System.Private.CoreLib/src/System/SpanHelpers.Byte.cs Lines 337 to 338 in 2a01ceb
After all of the inlining improvements made in .NET 6 and 7, are these still necessary and helping more than they hurt?
|
These [AggressiveOptimization] attributes were added as a workaround for #9120 |
I think we can remove them at least from However, we might need to check that |
SpanHelpers members which refuse to precompile (because they use
|
Moving to 8.0.0 as it depends on the planned change to make crossgen avx2-aware by default. |
I assume we can close this one as we now have only 3 [AO] in BCL:
|
dotnet/coreclr#22191 added a bunch of [AggressiveOptimization] attributes to methods throughout SpanHelpers and elsewhere that make heavy use of intrinsics, e.g.
runtime/src/libraries/System.Private.CoreLib/src/System/SpanHelpers.Byte.cs
Lines 337 to 338 in 2a01ceb
After all of the inlining improvements made in .NET 6 and 7, are these still necessary and helping more than they hurt?
category:design
theme:basic-cq
skill-level:beginner
cost:small
impact:small
The text was updated successfully, but these errors were encountered: