summaryrefslogtreecommitdiff
path: root/lib/Target/PowerPC/PPCAsmPrinter.cpp
diff options
context:
space:
mode:
authorTim Northover <tnorthover@apple.com>2014-05-26 17:22:07 +0000
committerTim Northover <tnorthover@apple.com>2014-05-26 17:22:07 +0000
commite0c2787cb770ecb3bb865a5cf51705fe2cd57441 (patch)
treeb415d2dd0797b5fadc0b29546294935a5436f975 /lib/Target/PowerPC/PPCAsmPrinter.cpp
parent4146695fb264a617a272f3dfd05b99b342e2b037 (diff)
downloadllvm-e0c2787cb770ecb3bb865a5cf51705fe2cd57441.tar.gz
llvm-e0c2787cb770ecb3bb865a5cf51705fe2cd57441.tar.bz2
llvm-e0c2787cb770ecb3bb865a5cf51705fe2cd57441.tar.xz
AArch64: force i1 to be zero-extended at an ABI boundary.
This commit is debatable. There are two possible approaches, neither of which is really satisfactory: 1. Use "@foo(i1 zeroext)" to mean an extension to 32-bits on Darwin, and 8 bits otherwise. 2. Redefine "@foo(i1)" to mean that the i1 is extended by the caller to 8 bits. This goes against the spirit of "zeroext" I think, but it's a bit of a vague construct anyway (by definition you're going to extend to the amount required by the ABI, that's why it's the ABI!). This implements option 2. The DAG machinery really isn't setup for the first (there's a fairly strong assumption that "zeroext" goes to at least the smallest register size), and even if it was the resulting DAG looks like it would be inferior in many cases. Theoretically we could add AssertZext nodes in the consumers of ABI-passed values too now, but this actually seems to make the code worse in practice by making truncation proceed in two steps. The code produced is equally valid if we continue to assume only the low bit is defined. Should fix PR19850 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@209637 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Target/PowerPC/PPCAsmPrinter.cpp')
0 files changed, 0 insertions, 0 deletions