Skip to content
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

Open
wants to merge 2 commits into
base: release/9.0-staging
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 3, 2025

Backport of #111000 to release/9.0-staging. Fixes storing of Vector3 into memory on mono-llvm-aot.

Customer Impact

  • Customer reported
  • Found internally

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

  • Yes
  • No

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.

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Jan 3, 2025
@jkurdek jkurdek added area-Codegen-LLVM-mono and removed area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI labels Jan 3, 2025
@jkurdek jkurdek requested review from matouskozak and tannergooding and removed request for fanyang-mono January 3, 2025 16:55
@jkurdek jkurdek self-assigned this Jan 3, 2025
Copy link
Contributor

Tagging subscribers to this area: @steveisok, @vitek-karas
See info in area-owners.md if you want to be subscribed.

@jkurdek
Copy link
Member

jkurdek commented Jan 3, 2025

/azp run runtime-extra-platforms

@dotnet dotnet deleted a comment from azure-pipelines bot Jan 3, 2025
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@carlossanlop
Copy link
Member

@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.

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a 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

@jeffschwMSFT jeffschwMSFT added the Servicing-consider Issue for next servicing release review label Jan 14, 2025
@jeffschwMSFT jeffschwMSFT added this to the 9.0.x milestone Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Codegen-LLVM-mono Servicing-consider Issue for next servicing release review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants