Providing the glue to map SDNode fast math sub flags to MachineInstr fast math sub flags.
The transfer itself is straightforward, so LGTM.
But if you can explain here for the record how we get from the IR FMF and function attributes to the DAG flags, that would be good. (And yes, I know you have some of the patches in progress to improve this.)
As part to the global explanation behind the design of this and other components in this stream of reviews, fast math flags are mined directly off of IR and propagated (or will be more so incrementally over time), so that we can rely on similar functionality without the use of the module level unsafe flag. The goal is to achieve parity in code generation and to propagate context sensitive guards over optimization and code generation so that relative functional IR attributes control these features. As in the summary this patch provides the mapping off of SDNode into MachineInstr so that we carry full context at the IR level from high level compilation into back ends.
I was actually more concerned with the non-obvious outcome in the affected regression tests because this particular case (sqrt estimate) just came up in:
In the 1st test (plain sqrt estimate), there's only a function attribute. The estimate transform is predicated on that function attribute and then applies 'reassoc' to new nodes as much as it could at the time it was implemented. That means it set that flag for binops (fadd/fmul), but not fma or rsqrt!
In the 2nd test (reciprocal sqrt estimate), the fdiv is marked 'fast', so the transform is able to propagate that to all of the created binop nodes (again, the 'fma' get nothing currently, but they should).
In summary, it's full of bugs.