Skip to content

WIP/IRGen: PCS for ARM VFP CC does not correctly handle HFAs #14304

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

compnerd
Copy link
Member

When materializing the implicit constructor containing a HFA, the VFP CC
will result in an incorrect attempt to coerce parameters to the
structure type. This causes an assertion in LLVM as we attempt to store
a structure by value into an alloca.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

When materializing the implicit constructor containing a HFA, the VFP CC
will result in an incorrect attempt to coerce parameters to the
structure type.  This causes an assertion in LLVM as we attempt to store
a structure by value into an alloca.
@compnerd
Copy link
Member Author

compnerd commented May 4, 2018

#15174 is more complete and supersedes this.

@compnerd compnerd closed this May 4, 2018
@compnerd compnerd deleted the ARM-VFP-SRoA branch May 4, 2018 23:54
@compnerd compnerd restored the ARM-VFP-SRoA branch May 4, 2018 23:55
@compnerd compnerd reopened this May 4, 2018
@compnerd
Copy link
Member Author

compnerd commented May 4, 2018

Oops, wrong PR

@shahmishal
Copy link
Member

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

  • How to change the base branch: (Link)
  • More detail about the branch update: (Link)

@tbkka
Copy link
Contributor

tbkka commented Jun 15, 2022

Looks like this is just a test update now? Besides CI testing, is anything needed to merge this?

@compnerd
Copy link
Member Author

I don't know if the underlying issue has been resolved. I think it would be good to check that, and we can decide to merge it with an XFAIL I suppose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants