On 2008 Oct 6, at 23:54, wman wrote:
just for the kicks i tried the new version of bytestring without -O2 and the results were even worse:
Yep, ByteString does a lot of stuff that is really bad when GHC isn't performing stream fusion --- but when it is, the code compiles down to tight machine code that can rival C.
is there a reason why -O2 shouldn't be made the default (and allowing to turn off optimizations by -O0 perhaps) ?
-O2 breaks on some platforms, I think.