summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support/LockFileManager.cpp
diff options
context:
space:
mode:
authorBill Schmidt <wschmidt@linux.vnet.ibm.com>2014-09-11 20:10:03 +0000
committerBill Schmidt <wschmidt@linux.vnet.ibm.com>2014-09-11 20:10:03 +0000
commitbe95fd535774a6f2bf0f6bbb3030562e58f97948 (patch)
tree38148be47d01877a4cc62255ae222b83af4d1043 /llvm/lib/Support/LockFileManager.cpp
parent88f098678273c98b8444521eece42aff79732ee5 (diff)
downloadbcm5719-llvm-be95fd535774a6f2bf0f6bbb3030562e58f97948.tar.gz
bcm5719-llvm-be95fd535774a6f2bf0f6bbb3030562e58f97948.zip
[PATCH, PowerPC] Accept 'U' and 'X' constraints in inline asm
Inline asm may specify 'U' and 'X' constraints to print a 'u' for an update-form memory reference, or an 'x' for an indexed-form memory reference. However, these are really only useful in GCC internal code generation. In inline asm the operand of the memory constraint is typically just a register containing the address, so 'U' and 'X' make no sense. This patch quietly accepts 'U' and 'X' in inline asm patterns, but otherwise does nothing. If we ever unexpectedly see a non-register, we'll assert and sort it out afterwards. I've added a new test for these constraints; the test case should be used for other asm-constraints changes down the road. llvm-svn: 217622
Diffstat (limited to 'llvm/lib/Support/LockFileManager.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud