summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
diff options
context:
space:
mode:
authorTim Northover <tnorthover@apple.com>2016-04-14 17:03:29 +0000
committerTim Northover <tnorthover@apple.com>2016-04-14 17:03:29 +0000
commitcdf1529c010d28a9102f770727cbdc2f74768de2 (patch)
treeb4647f11f0499f378904e12cf597d604d34e18e0 /lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
parentadd4a274ba05031f0fb62a9ac430d78e2da6f743 (diff)
downloadbcm5719-llvm-cdf1529c010d28a9102f770727cbdc2f74768de2.tar.gz
bcm5719-llvm-cdf1529c010d28a9102f770727cbdc2f74768de2.zip
AArch64: expand cmpxchg after regalloc at -O0.
FastRegAlloc works only at the basic-block level and spills all live-out registers. Unfortunately for a stack-based cmpxchg near the spill slots, this can perpetually clear the exclusive monitor, which means the cmpxchg will never succeed. I believe the only way to handle this within LLVM is by expanding the loop post-regalloc. We don't want this in general because it severely limits the optimisations that can be done, so we limit this to -O0 compilations. It's an ugly hack, and about the one good point in the whole mess is that we can treat all cmpxchg operations in the most naive way possible (seq_cst, no clrex faff) without affecting correctness. Should fix PR25526. llvm-svn: 266339
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud