This call to reassociateReduction is used by both fminnum/fmaxnum and fminimum/fmaximum. In adding support for fminimum/fmaximum we appear to be fixing the use of an incorrect reduction type, which should have only applied to minnum/maxnum.
I also believe that it doesn't need nsz and reassoc to perform the reassociation. For float min/max it should always be valid.
Since we no longer check any flags for doing the reassociation, can you pls add a test without the fast flag as well?