summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2019-02-01 19:08:59 +0000
committerPhilip Reames <listmail@philipreames.com>2019-02-01 19:08:59 +0000
commit5503e4f9b94ed59089971f573328f1866e1bc6e1 (patch)
treedce59b346105b0c82a832485038eb355ddf0473d /llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp
parent7f29195c3fe0350d1e47ae8629d9db3ed16690ff (diff)
downloadbcm5719-llvm-5503e4f9b94ed59089971f573328f1866e1bc6e1.tar.gz
bcm5719-llvm-5503e4f9b94ed59089971f573328f1866e1bc6e1.zip
Fix a bug in the definition of isUnordered on MachineMemOperand
Background: At the moment, we record the AtomicOrdering of an access in the MMO, but also mark any atomic access as volatile in SelectionDAG. GlobalISEL keeps the two separate, but currently doesn't know how to lower an atomic G_LOAD at all. See https://reviews.llvm.org/D57601 for context. The definition used for unordered was only checking volatility, not atomicity. As noted above, all atomic MMOs are currently also volatile, so this is a latent bug only. Copy the definition used in IR, after auditing the two (2) uses of the function to be sure the desired semantics are the same. Differential Revision: https://reviews.llvm.org/D57593 llvm-svn: 352898
Diffstat (limited to 'llvm/lib/Transforms/Vectorize/SLPVectorizer.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud