This is an archive of the discontinued LLVM Phabricator instance.

[ARM] Fix Neon vector type alignment to 64-bit
ClosedPublic

Authored by javed.absar on Jun 1 2017, 10:06 AM.

Details

Summary

This is restricted version of patch - https://reviews.llvm.org/D33205
that I reverted as it was leading to ABI breaks on darwin etc.
This patch restricts the fix to AAPCS only.

Diff Detail

Repository
rL LLVM

Event Timeline

javed.absar created this revision.Jun 1 2017, 10:06 AM
srhines added inline comments.Jun 1 2017, 10:19 AM
test/CodeGen/neon-aapcs-align.c
9 ↗(On Diff #101042)

Can you make sure that an Android triple doesn't trigger this? I worry because I am not sure what getABI() will return in that case.

javed.absar added inline comments.Jun 1 2017, 1:01 PM
test/CodeGen/neon-aapcs-align.c
9 ↗(On Diff #101042)

Could you please elaborate.There is a test already 'armv7-none-linux-androideabi'.

lib/Basic/Targets.cpp:5357:: case llvm::Triple::Android:
sets it to aapcs-linux

srhines edited edge metadata.Jun 1 2017, 1:34 PM

LGTM

test/CodeGen/neon-aapcs-align.c
9 ↗(On Diff #101042)

Yes, but you are also passing -target-abi here. I wanted confirmation that this will always be passed on the cc1 line. I think the line from Targets.cpp confirms that this is going to be the case (unless someone explicitly passes a different -target-abi option to cc1. Thanks.

Thanks Stephen.
Vedant, Diana : Does this look ok to you as well?

rovka edited edge metadata.Jun 2 2017, 2:55 AM

It certainly seems more restrictive than the previous patch, so I think it should be ok. @rengolin probably understands the subtleties here a bit better than I do.

Hi Renato. Please could you have a look at this. I had a LGTM from @rovka and @srhines but need final one from you.
Thanks, Javed.

rengolin added inline comments.Jun 5 2017, 1:35 AM
test/CodeGen/neon-aapcs-align.c
9 ↗(On Diff #101042)

This is odd. On Android alone, it should be 128. In anything + aapcs, it should be 64, including Android. Explicit behaviour trumps default behaviour.

Do we have tests to make sure that the right CC1 flags are passed down?

We need two types of tests here: default behaviour and overriden behaviour.

I'd also add a GNUEABI and FreeBSD lines, because they're sufficiently different from the ones above.

Hi Renato:
I have made changes as suggested (unless I got somethings wrong).

  1. Now, except for android, AAPCS => 64-bit alignment
  2. The fix relies only on the triple for I am not sure if 'right cc1' flag test is needed.
  3. Added gnueabi and FreeBSD as suggested.

Please have a look. Thanks.
--Javed

rengolin edited edge metadata.Jun 6 2017, 9:36 AM

@srhines: Do you need Android to *always* be 64-bit, even if someone forces aapcs with it?

@srhines: Do you need Android to *always* be 64-bit, even if someone forces aapcs with it?

128-bit always. We don't support "multiple" ABIs. There is only one, and it makes sense to not allow people to choose something that can't work.

This revision is now accepted and ready to land.Jun 6 2017, 9:45 AM
This revision was automatically updated to reflect the committed changes.