[PATCH] D57601: Seperate volatility and atomicity/ordering in SelectionDAG

[Philip Reames via Phabricator via llvm-commits]

reames added a comment.

Question for Reviewers: Going through uses of isVolatile in backend code, I see suspicious bits in Lania, ARM, and Hexagon.  What's the best way to handle this?  I can easily apply the workaround I mention for out of tree backends, or I could make them equally conservative for isAtomic.  The other in tree backends appear to be fine, though I'd welcome review from folks knowledgeable of non-x86 backends.


CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D57601/new/

https://reviews.llvm.org/D57601