[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.

I’m not seeing how FP instructions can not carry flags. The IR semantics are defined to be strict FP unless explicitly relaxed.

The point of the AnyDefined state bit is to avoid pessimizing when the actual flags object has not been explicitly written to, e.g default constructed. When instantiating from a math operator that must obey strict semantics by default, the flags must also reflect those same semantics. Now if FPMathOperator also has a 3rd “undefined state” then it’s different.


https://reviews.llvm.org/D51145