search for: ffastmath

...11.2016 09:51, Ristow, Warren wrote: > Those are all good points. Your reassociation point in the context of > inlining is particularly interesting. > > > > FWIW, we also have a case where a customer wants '-fno-associative-math' > to suppress reassociation under '-ffastmath'. It would take me a while > to find the specifics of the issue, but it was (if my memory is right) > more of a real use-case. (That is to say, the code that was "failing" > due to reassociation didn't have an obvious fix like the reciprocal > situation, here, other...

...2016 09:51, Ristow, Warren wrote: > Those are all good points. Your reassociation point in the context of > inlining is particularly interesting. > > > > FWIW, we also have a case where a customer wants '-fno-associative-math' > to suppress reassociation under '-ffastmath'. It would take me a while > to find the specifics of the issue, but it was (if my memory is right) > more of a real use-case. (That is to say, the code that was "failing" > due to reassociation didn't have an obvious fix like the reciprocal > situation, here, other...

...are all good points. Your reassociation point in the context of >>> inlining is particularly interesting. >>> >>> >>> >>> FWIW, we also have a case where a customer wants '-fno-associative-math' >>> to suppress reassociation under '-ffastmath'. It would take me a while >>> to find the specifics of the issue, but it was (if my memory is right) >>> more of a real use-case. (That is to say, the code that was "failing" >>> due to reassociation didn't have an obvious fix like the reciprocal >...

> On Nov 16, 2016, at 10:04 PM, Ristow, Warren <warren.ristow at sony.com> wrote: > > > Can you elaborate what kind of runtime failure is the reciprocal transformation triggering? > > Yes. It was along the lines of: > > { > float x = a / c; > float y = b / c; > > if (y == 1.0f) { > // do some processing for when

...ing the semantics of 'fast' flag implying all fast-math-flags Those are all good points. Your reassociation point in the context of inlining is particularly interesting. FWIW, we also have a case where a customer wants '-fno-associative-math' to suppress reassociation under '-ffastmath'. It would take me a while to find the specifics of the issue, but it was (if my memory is right) more of a real use-case. (That is to say, the code that was "failing" due to reassociation didn't have an obvious fix like the reciprocal situation, here, other than to turn off fas...

...all fast-math-flags > > > > Those are all good points. Your reassociation point in the context of > inlining is particularly interesting. > > > > FWIW, we also have a case where a customer wants '-fno-associative-math' > to suppress reassociation under '-ffastmath'. It would take me a > while to find the specifics of the issue, but it was (if my memory is > right) more of a real use-case. (That is to say, the code that was "failing" > due to reassociation didn't have an obvious fix like the reciprocal > situation, here, oth...

...all good points. Your reassociation point in the context of >>> inlining is particularly interesting. >>> >>> >>> >>> FWIW, we also have a case where a customer wants '-fno-associative-math' >>> to suppress reassociation under '-ffastmath'. It would take me a >>> while to find the specifics of the issue, but it was (if my memory is >>> right) more of a real use-case. (That is to say, the code that was "failing" >>> due to reassociation didn't have an obvious fix like the reciprocal &...