binary sizes

[Adam Megacz]

Andrew Haley <aph@redhat.com> writes:
>  > right?  Is it really supposed to consume 20% of the binary?
> Yes.

Ugh.


> Perhaps, but we're moving to removing the traditional stack chain by
> compiling with omit-frame-pointer: once that move is complete, DWARF2
> unwinder data will be needed everywhere.

Hrm, this sounds interesting, but I thought that fomit-frame-pointer
only drops the frame pointer for functions that don't need it.  Do you
mean that DWARF2 info is needed in order to use a debugger or get
stack traces?  I can live without those...


> Some of the reflection data is used by the gc.

The GC?  That's wierd... what for?  Determining pointerfree regions?

  - a