This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Getting rid of -fno-unit-at-a-time [Was Re: RFC: Preserving order of functions and top-level asms via cgraph]
- From: Andrew Haley <aph at redhat dot com>
- To: Steven Bosscher <stevenb at suse dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 11 Apr 2005 11:31:52 +0100
- Subject: Re: Getting rid of -fno-unit-at-a-time [Was Re: RFC: Preserving order of functions and top-level asms via cgraph]
- References: <20050410221314.GA11215@nevyn.them.org><4259AE7A.8080502@codesourcery.com><16986.20203.730292.812639@cuddles.cambridge.redhat.com><200504111224.12449.stevenb@suse.de>
Steven Bosscher writes:
> On Monday 11 April 2005 12:18, Andrew Haley wrote:
> > Mark Mitchell writes:
> > > Your primary objective (get rid of -fno-unit-at-a-time) is one that I
> > > strongly support.
> >
> > I have a problem with getting rid of -fno-unit-at-a-time. Sometimes
> > we compile huge Java programs; however, keeping all the method bodies
> > consumes vast amouts of memory.
>
> This is what C++ does now too. Why would this be a problem
> for Java but not for C++?
I don't know why it's not a problem for C++; I do know why it's a
problem for Java. Perhaps the files we're compiling are larger.
Certainly jarfiles can get to be very large, and once gcc's store
starts to exceed the size of physical memory things can get very
painful.
Andrew.