object code blow up by optimization

[Christian Maeder]

Christian Maeder wrote:
>>> I've a few files that produce ten times bigger .o files when compiled 
>>> with optimization (-O). This blow-up prevents linking on a mac.
> 
> I had some success by adding
> 
> {-# OPTIONS -fno-strictness #-}

This option did finally not help.

The code bloat may have something to do with unfolding (or other 
optimizations) within method instances.

We have about 400 data types with (partly overlapping) Typeable and 
ShATermConvertible instances. I now changed a member function with a 
default definition to a global function and the binaries became smaller.

I could not investigate the problem any further, yet.

Cheers Christian