summaryrefslogtreecommitdiffstats
path: root/llvm/lib/MC/MCObjectStreamer.cpp
diff options
context:
space:
mode:
authorEli Friedman <efriedma@codeaurora.org>2018-07-17 20:38:11 +0000
committerEli Friedman <efriedma@codeaurora.org>2018-07-17 20:38:11 +0000
commite15a111ba0df12b4ad24c64cf9daef031fba007e (patch)
tree2f7c2819b3b6775d676dccbde2d9e408aece7c8b /llvm/lib/MC/MCObjectStreamer.cpp
parent061b4af998fc4a211566505555403806c373886a (diff)
downloadbcm5719-llvm-e15a111ba0df12b4ad24c64cf9daef031fba007e.tar.gz
bcm5719-llvm-e15a111ba0df12b4ad24c64cf9daef031fba007e.zip
[LangRef] Clarify semantics of load metadata.
We need to explicitly state what happens when an invariant promised by load metadata is violated at runtime, since it's come up repeatedly. It's possible we want to specify that the result of the load is poison in some cases, rather than undefined behavior, if the constraint is violated. That would allow preserving the metadata when the load is hoisted, but doesn't allow propagating metadata based on control flow. We currently do transforms based on control flow for nonnull metadata (in PromoteMemToReg). Differential Revision: https://reviews.llvm.org/D47854 llvm-svn: 337325
Diffstat (limited to 'llvm/lib/MC/MCObjectStreamer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud