This is the mail archive of the
mailing list for the GCC project.
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: gcc at gcc dot gnu dot org
- Date: Mon, 11 Apr 2005 11:18:19 +0100
- Subject: 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.firstname.lastname@example.org>
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. So, we sometimes need to generate
code for each class as soon as it is parsed and then free the bodies.
Might it still be possible for a front end to force all pending code
to be generated, even with -fno-unit-at-a-time gone?