| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Tagging subscribers to this area: @steveisok, @vitek-karas |
Sorry, something went wrong.
|
/azp run runtime-extra-platforms |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm. please get a code review. we will take for consideration in 9.0.x
Sorry, something went wrong.
|
@jkurdek can you take a look at the CI failures? we can merge when ready |
Sorry, something went wrong.
|
/azp run runtime-extra-platforms |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, something went wrong.
|
/ba-g runtime-extra-platforms failures are known and unrelated |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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.