DAG: Look through fneg when trying to create unsafe minnum/maxnum
This makes most sense for isFNegFree targets, but shouldn't make things worse without it. This avoids AMDGPU test regressions in a future patch. For some reason APFloat::compareAbsoluteValue is private, so compute the neg of the constants.
Loading
Please sign in to comment