This is the mail archive of the
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: Steven Bosscher <stevenb at suse dot de>
- To: gcc at gcc dot gnu dot org
- Cc: Andrew Haley <aph at redhat dot com>
- Date: Mon, 11 Apr 2005 12:24:12 +0200
- Subject: Re: Getting rid of -fno-unit-at-a-time [Was Re: RFC: Preserving order of functions and top-level asms via cgraph]
- Organization: SUSE Labs
- References: <20050410221314.GA11215@nevyn.them.org> <4259AE7A.email@example.com> <firstname.lastname@example.org>
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++?
> So, we sometimes need to generate
> code for each class as soon as it is parsed and then free the bodies.
(The proper solution is of course to have an IR that we can
stream to disk, *sigh* ;-)