[PATCH] D51145: make copyFMF consistent with AnyDefined for detection of any FMF flag set to true

[Amara Emerson via Phabricator via llvm-commits]

aemerson added a comment.

Ok, to me it seems like instructions for which fast math flags can't apply shouldn't be classed as FPMathOperators. insertelement/extractelement are just moving raw bits. If we disallowed those instruction types in the FPMathOperator classof() then this problem should go away, and we don't incorrectly relax FP semantics like in the case I pointed out.


https://reviews.llvm.org/D51145