This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: binary sizes

From: Adam Megacz <megacz at gcc dot gnu dot org>
To: java at gcc dot gnu dot org
Date: Wed, 18 Feb 2004 02:43:00 -0800
Subject: Re: binary sizes
Organization: Myself
References: <E1AtH4K-0001y4-00@megacz.com> <16435.15008.181570.668731@cuddles.cambridge.redhat.com>

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

Follow-Ups:
- Re: binary sizes
  - From: Andrew Haley

References:
- binary sizes
  - From: Adam Megacz
- binary sizes
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]