summaryrefslogtreecommitdiffstats
path: root/lldb/source/Commands/CommandObjectProcess.cpp
diff options
context:
space:
mode:
authorJakob Stoklund Olesen <stoklund@2pi.dk>2012-08-29 20:48:45 +0000
committerJakob Stoklund Olesen <stoklund@2pi.dk>2012-08-29 20:48:45 +0000
commit813a109fa5b5f41534e0fcc22cfbaa0d0888c05b (patch)
tree3ce8db6d3c2ca4d7a9a1832fb196001fa65ea30f /lldb/source/Commands/CommandObjectProcess.cpp
parent84ee8bf34905f4bc0f8d296659bc16b138ca51cb (diff)
downloadbcm5719-llvm-813a109fa5b5f41534e0fcc22cfbaa0d0888c05b.tar.gz
bcm5719-llvm-813a109fa5b5f41534e0fcc22cfbaa0d0888c05b.zip
Don't move normal loads across volatile/atomic loads.
It is technically allowed to move a normal load across a volatile load, but probably not a good idea. It is not allowed to move a load across an atomic load with Ordering > Monotonic, and we model those with MOVolatile as well. I recently removed the mayStore flag from atomic load instructions, so they don't need a pseudo-opcode. This patch makes up for the difference. llvm-svn: 162857
Diffstat (limited to 'lldb/source/Commands/CommandObjectProcess.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud