In case anyone else was following this, I've discovered the source of
the differing output. I had made some assumptions about when some
code would be executed based upon faulty reasoning. Without
pre-inlining those assumptions happened to hold, but they did not when
pre-inlining was enabled.
John
| When compiled with -fno-pre-inlining, my test program gives a
| different result than compiled without (0.988... :: Double, compared
| to 1.0). It's numerical code, and was originally compiled with
That's entirely unexpected. I am very surprised that turning off pre-inlining
a) affects
Simon,
Thanks for the quick reply, and also the link. I'll be sure to read
it. I don't know what pre-inlining is; I was testing different
compiler options with acovea, which indicated the performance boost.
When I tried it myself, I noticed the differing value.
I'm pretty sure the affected
