Fixing an issue with the CPUID check for BMI1/BMI2 and LZCNT #40615
Conversation
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
Dotnet-GitSync-Bot
added
the
area-CodeGen-coreclr
Member
Author
|
CC. @jkotas |
jnyrup
reviewed
Sep 10, 2020
| __cpuid(cpuidInfo, 0x80000001); | ||
|
|
||
| if ((cpuidInfo[3] & (1 << 5)) != 0) // LZCNT | ||
| if ((cpuidInfo[ECX] & (1 << 5)) != 0) // LZCNT |
Contributor
There was a problem hiding this comment.
The commit description only mentions changes for BMI1/2.
Is this change from 3 to ECX=2 for LZCNT intentional?
Contributor
There was a problem hiding this comment.
Nevermind, spotted the comment
// LZCNT - ECX bit 5
on line 1351
tannergooding
changed the title
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
#40167 redid part of the CPUID logic as part of exposing X86Base.CpuId. As part of that, the check for BMI1/2 was updated to use an incorrect index.
This fixes the logic to use 4 named constants during lookup to help avoid this issue.