-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/9.0-staging] [mono] [llvm-aot] Fixed storing Vector3 into memory #111069
base: release/9.0-staging
Are you sure you want to change the base?
[release/9.0-staging] [mono] [llvm-aot] Fixed storing Vector3 into memory #111069
Conversation
Tagging subscribers to this area: @steveisok, @vitek-karas |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
@jkurdek friendly reminder that today's code complete for the Feb 2025 Release. Please merge this change by 4pm PT if you'd like it included in that release version. Otherwise, it will have to wait until next month. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. please get a code review. we will take for consideration in 9.0.x
Backport of #111000 to release/9.0-staging. Fixes storing of Vector3 into memory on mono-llvm-aot.
Customer Impact
Reported in #110820. Storing Vector3 into memory was is working incorrectly when using mono aot llvm. Instead of being saved as Vector3 it is saved as Vector4 (Vector3 + trailing 0) effectively overwriting the next memory cell with 0. Customer experienced their data being overwritten with 0s.
Regression
Regression introduced in #97416. This change implemented some intrinsics for Vector3 - for those intrinsics purposes Vector3 is being represented as Vector4 (Vector3 + 0).
Testing
Added test a new test verifying that saving Vector3 works correctly.
Risk
Low. Change applies only to mono aot llvm Vector3 save to memory path.