Ensure that math calls into the CRT are tracked as needing vzeroupper #112011
+112
−79
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.
The root issue was that
GenTreeCall::NeedsVzeroupper
was only looking atIsPInvoke()
methods, while calls likeMath.Sin
are represented as regularCT_USERCALL
, thus we lost track of the fact that this was not actually in managed.This then resolves #111016 by ensuring that we correctly mark such calls as being "special" (via
GTF_CALL_M_SPECIAL_INTRINSIC
) which then allows us to decide to do the additional signature checking and determine that avzeroupper
is needed.If any of these calls are later moved to managed, then we can avoid the
vzeroupper
by not marking these particular cases as "special". This already applies to cases likeSqrt
which are never rewritten back as user calls or cases like Max where we know the fallback is in managed, rather than into the C runtime.