[release/9.0-rc1] JIT: fix unused operand marking in LowerHWIntrinsicTernaryLogic #106574
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.
Backport of #106555 to release/9.0-rc1
/cc @AndyAyersMS
Customer Impact
Found by Antigen (internal exploratory test generator).
Certain uses of AVX512F's Ternary Logic will lead to silent bad code generation.
Regression
Introduced fairly recently, in #104517.
Testing
The fix was validated on the Antigen test case, and that case is now included in our regression suite.
We likely need to pay more attention in reviews and testing when considering code where operands can be swapped, as it's easy to lose track of which one is which.
Risk
Low. Only impacts a handful of AVX512-specific intrinsics. But note TernaryLogic lowers to a powerful new instruction (
vpternlog{d,q}
) and we are increasingly shaping our IR to take advantage of it, when running on AVX-512 hardware.IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.