summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2015-12-17 18:50:50 +0000
committerPhilip Reames <listmail@philipreames.com>2015-12-17 18:50:50 +0000
commit15145fb7b17d0499a706f8bb830dad272a06937d (patch)
treec9c45a31defa100b23fa82b04aaa58ae58cfd3d9 /lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py
parent42c1e2923664d298970be6b0f8b21790859499e9 (diff)
downloadbcm5719-llvm-15145fb7b17d0499a706f8bb830dad272a06937d.tar.gz
bcm5719-llvm-15145fb7b17d0499a706f8bb830dad272a06937d.zip
[EarlyCSE] DSE of atomic unordered stores
The rules for removing trivially dead stores are a lot less complicated than loads. Since we know the later store post dominates the former and the former dominates the later, unless the former has side effects other than the actual store, we can remove it. One slightly surprising thing is that we can freely remove atomic stores, even if the later one isn't atomic. There's no guarantee the atomic one was every visible. For the moment, we don't handle DSE of ordered atomic stores. We could extend the same chain of reasoning to them, but the catch is we'd then have to model the ordering effect without a store instruction. Since our fences are a stronger than our operation orderings, simple using a fence isn't an obvious win. This arguable calls for a refinement in our fence specification, but that's (much) later work. Differential Revision: http://reviews.llvm.org/D15352 llvm-svn: 255914
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud