summaryrefslogtreecommitdiffstats
path: root/llvm/lib/MC/StringTableBuilder.cpp
diff options
context:
space:
mode:
authorUlrich Weigand <ulrich.weigand@de.ibm.com>2016-02-19 14:10:21 +0000
committerUlrich Weigand <ulrich.weigand@de.ibm.com>2016-02-19 14:10:21 +0000
commitcfa1d2b49d7b3f42833dc16cc5bfbaf3d9ba74a8 (patch)
tree4233bbf11c39e819da58139267aa24675acf4b65 /llvm/lib/MC/StringTableBuilder.cpp
parent611d2e4ee6a5150b45659abafd76e5917d4382a7 (diff)
downloadbcm5719-llvm-cfa1d2b49d7b3f42833dc16cc5bfbaf3d9ba74a8.tar.gz
bcm5719-llvm-cfa1d2b49d7b3f42833dc16cc5bfbaf3d9ba74a8.zip
[SystemZ] Fix ABI for i128 argument and return types
According to the SystemZ ABI, 128-bit integer types should be passed and returned via implicit reference. However, this is not currently implemented at the LLVM IR level for the i128 type. This does not matter when compiling C/C++ code, since clang will implement the implicit reference itself. However, it turns out that when calling libgcc helper routines operating on 128-bit integers, LLVM will use i128 argument and return value types; the resulting code is not compatible with the ABI used in libgcc, leading to crashes (see PR26559). This should be simple to fix, except that i128 currently is not even a legal type for the SystemZ back end. Therefore, common code will already split arguments and return values into multiple parts. The bulk of this patch therefore consists of detecting such parts, and correctly handling passing via implicit reference of a value split into multiple parts. If at some time in the future, i128 becomes a legal type, this code can be removed again. This fixes PR26559. llvm-svn: 261325
Diffstat (limited to 'llvm/lib/MC/StringTableBuilder.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud