summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
diff options
context:
space:
mode:
authorJeremy Morse <jeremy.morse.llvm@gmail.com>2019-02-12 10:54:30 +0000
committerJeremy Morse <jeremy.morse.llvm@gmail.com>2019-02-12 10:54:30 +0000
commitb33a5c7347fce57f58ce5f0dbb086a11caa5220f (patch)
treeede3fb1ffcf119335d0a8f79059d6f151ca58ddb /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
parentbbd2f972930e4ae99d5fff68122b5b7cec6aace7 (diff)
downloadbcm5719-llvm-b33a5c7347fce57f58ce5f0dbb086a11caa5220f.tar.gz
bcm5719-llvm-b33a5c7347fce57f58ce5f0dbb086a11caa5220f.zip
[DebugInfo] Don't salvage load operations (PR40628).
Salvaging a redundant load instruction into a debug expression hides a memory read from optimisation passes. Passes that alter memory behaviour (such as LICM promoting memory to a register) aren't aware of these debug memory reads and leave them unaltered, making the debug variable location point somewhere unsafe. Teaching passes to know about these debug memory reads would be challenging and probably incomplete. Finding dbg.value instructions that need to be fixed would likely be computationally expensive too, as more analysis would be required. It's better to not generate debug-memory-reads instead, alas. Changed tests: * DeadStoreElim: test for salvaging of intermediate operations contributing to the dead store, instead of salvaging of the redundant load, * GVN: remove debuginfo behaviour checks completely, this behaviour is still covered by other tests, * InstCombine: don't test for salvaged loads, we're removing that behaviour. Differential Revision: https://reviews.llvm.org/D57962 llvm-svn: 353824
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud