summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python/interface/SBValue.i
diff options
context:
space:
mode:
authorHal Finkel <hfinkel@anl.gov>2014-12-08 22:54:22 +0000
committerHal Finkel <hfinkel@anl.gov>2014-12-08 22:54:22 +0000
commitaa10b3caaf813ba9e4a26ee73a1586022e98d258 (patch)
tree0813c26840fcd945e7a1cf758d1e8d03b7fe47b8 /lldb/scripts/Python/interface/SBValue.i
parenta15a6dc78e46163bf10aa28fe05cb646a6d23b6e (diff)
downloadbcm5719-llvm-aa10b3caaf813ba9e4a26ee73a1586022e98d258.tar.gz
bcm5719-llvm-aa10b3caaf813ba9e4a26ee73a1586022e98d258.zip
[PowerPC] Don't use a non-allocatable register to implement the 'cc' alias
GCC accepts 'cc' as an alias for 'cr0', and we need to do the same when processing inline asm constraints. This had previously been implemented using a non-allocatable register, named 'cc', that was listed as an alias of 'cr0', but the infrastructure does not seem to support this properly (neither the register allocator nor the scheduler properly accounts for the alias). Instead, we can just process this as a naming alias inside of the inline asm constraint-processing code, so we'll do that instead. There are two regression tests, one where the post-RA scheduler did the wrong thing with the non-allocatable alias, and one where the register allocator did the wrong thing. Fixes PR21742. llvm-svn: 223708
Diffstat (limited to 'lldb/scripts/Python/interface/SBValue.i')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud