Skip to content

Conversation

@davidwrighton
Copy link
Member

  • A refactoring during crossgen2 production in the recent pr broke the unsupported instruction set mode for crossgen
  • Tested via manual inspection of the JIT\HardwareIntrinsics\X86\Avx\Sqrt_r test.

@davidwrighton
Copy link
Member Author

@MichalStrehovsky This fixes the issue you noted after the #33274 was merged.

#endif
{
_actualInstructionSetSupported.AddInstructionSet(instructionSet);
_actualInstructionSetUnsupported.AddInstructionSet(instructionSet);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, the classic if (cond) { stuff } else { exact same stuff } attacks again

Copy link
Member

@MichalStrehovsky MichalStrehovsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Maybe this is going to address #34628?

@davidwrighton davidwrighton merged commit 46c47c9 into dotnet:master Apr 7, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
@davidwrighton davidwrighton deleted the unsupportedInstructionSet branch April 20, 2021 17:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants