Skip to content

Conversation

@JonPsson1
Copy link
Contributor

When an integer argument is promoted and not split (like i72 -> i128 on a new machine with vector support), the SlotVT should be i128, which is stored in VT - not ArgVT.

Fixes #81417

@JonPsson1 JonPsson1 requested a review from uweigand February 21, 2024 09:20
Copy link
Member

@uweigand uweigand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@JonPsson1 JonPsson1 merged commit 9c0e45d into llvm:main Feb 21, 2024
@JonPsson1 JonPsson1 deleted the StackArgVT branch February 21, 2024 15:26
@uweigand uweigand added this to the LLVM 18.X Release milestone Feb 26, 2024
@uweigand
Copy link
Member

/cherry-pick 9c0e45d

llvmbot pushed a commit to llvmbot/llvm-project that referenced this pull request Feb 26, 2024
When an integer argument is promoted and *not* split (like i72 -> i128 on a new machine with vector support), the SlotVT should be i128, which is stored in VT - not ArgVT. Fixes llvm#81417 (cherry picked from commit 9c0e45d)
@llvmbot
Copy link
Member

llvmbot commented Feb 26, 2024

/pull-request #83021

llvmbot pushed a commit to llvmbot/llvm-project that referenced this pull request Feb 26, 2024
When an integer argument is promoted and *not* split (like i72 -> i128 on a new machine with vector support), the SlotVT should be i128, which is stored in VT - not ArgVT. Fixes llvm#81417 (cherry picked from commit 9c0e45d)
@pointhex pointhex mentioned this pull request May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants