[release/8.0-rc2] JIT: Fix invalid containment of vector broadcasts #92371
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 #92333 to release/8.0-rc2
/cc @jakobbotsch
Customer Impact
The JIT may generate bad code for
VectorXYZ<T>.Create(x)
wherex
is a memory location of smaller size thanT
. In that case the JIT may incorrectly read the memory location using the larger typeT
.For example,
Vector128<int>.Create(x.ShortField)
may generate bad code reading 4 bytes fromShortField
instead of just 2. Customer reported in #83387.Testing
Regression test included.
Risk
Low, disables the JIT's containment optimization in the affected cases.