diff options
author | Hal Finkel <hfinkel@anl.gov> | 2014-01-08 21:52:02 +0000 |
---|---|---|
committer | Hal Finkel <hfinkel@anl.gov> | 2014-01-08 21:52:02 +0000 |
commit | 2150e3a743f8da5322366f7ec23a072c893edc29 (patch) | |
tree | 3f19b458c2966768648b9b7e1e0f4c94de0478b4 /llvm/lib/Analysis/ModuleDebugInfoPrinter.cpp | |
parent | a64ee177a01fa84a4b602deca32f07db134c9962 (diff) | |
download | llvm-2150e3a743f8da5322366f7ec23a072c893edc29.zip llvm-2150e3a743f8da5322366f7ec23a072c893edc29.tar.gz llvm-2150e3a743f8da5322366f7ec23a072c893edc29.tar.bz2 |
Conservatively handle multiple MMOs in MIsNeedChainEdge
MIsNeedChainEdge, which is used by -enable-aa-sched-mi (AA in misched), had an
llvm_unreachable when -enable-aa-sched-mi is enabled and we reach an
instruction with multiple MMOs. Instead, return a conservative answer. This
allows testing -enable-aa-sched-mi on x86.
Also, this moves the check above the isUnsafeMemoryObject checks.
isUnsafeMemoryObject is currently correct only for instructions with one MMO
(as noted in the comment in isUnsafeMemoryObject):
// We purposefully do no check for hasOneMemOperand() here
// in hope to trigger an assert downstream in order to
// finish implementation.
The problem with this is that, had the candidate edge passed the
"!MIa->mayStore() && !MIb->mayStore()" check, the hoped-for assert would never
happen (which could, in theory, lead to incorrect behavior if one of these
secondary MMOs was volatile, for example).
llvm-svn: 198795
Diffstat (limited to 'llvm/lib/Analysis/ModuleDebugInfoPrinter.cpp')
0 files changed, 0 insertions, 0 deletions