On Sat, 2006-07-01 at 16:36 +0100, Ian Lynagh wrote:
> [resending as the original seems to have been silently eaten;
> attachements are at http://urchin.earth.li/~ian/splitting/ ]
>
> On Fri, Jun 30, 2006 at 03:45:57PM -0700, mvanier wrote:
> >
> > I'm at a loss here. Somehow, the SplitObjs opti
On Fri, Jun 30, 2006 at 03:45:57PM -0700, mvanier wrote:
>
> I'm at a loss here. Somehow, the SplitObjs option doesn't seem to be doing
> the job. Any suggestions would be appreciated.
It looks like gcc 4.1 is floating all the
__asm__("\n__stg_split_marker:");
results to the top of the
[resending as the original seems to have been silently eaten;
attachements are at http://urchin.earth.li/~ian/splitting/ ]
On Fri, Jun 30, 2006 at 03:45:57PM -0700, mvanier wrote:
>
> I'm at a loss here. Somehow, the SplitObjs option doesn't seem to be doing
> the job. Any suggestions would be
Yup, that's the problem all right. Recompiling ghc with
--with-gcc=/usr/bin/gcc-3.3 (on Debian) gives small executables. Thanks, Ian!
What a relief -- I was running multiple instances of hnop and it was chewing up
all of my memory ;-) Perhaps an hnop server might be a useful future direction
[Moving to haskell-cafe]
OK, after going through this several times, here's what I've found:
1) The Debian linux build of haskell produces large executables.
2) The generic x86 binary distribution produces smallish executables
(383765 bytes; still kind of large; stripped it's 191584 bytes).
3
