This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [wwwdocs] Add unit-at-a-time entry
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Jan Hubicka <jh at suse dot cz>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sun, 27 Jul 2008 00:14:58 +0200 (CEST)
- Subject: Re: [wwwdocs] Add unit-at-a-time entry
- References: <20080725115340.GA14302@kam.mff.cuni.cz>
On Fri, 25 Jul 2008, Jan Hubicka wrote:
> Index: changes.html
> ===================================================================
> + <li><code>-fno-unit-at-a-time</code> code has been
> + removed from GCC. The command line option is still accepted
> + and imply <code>-fno-toplevel-reorder</code> and
> + <code>-fno-section-anchors</code>.</li>
How about slightly rephrasing this as follows?
<li>GCC now always operates in unit-at-a-time mode, which allows the
compiler to consider information gained from later functions in the
file when compiling a function. For backwards compatibility, the
<code>-fno-unit-at-a-time</code> command-line option is still accepted
and implies <code>-fno-toplevel-reorder</code> and
<code>-fno-section-anchors</code>.</li>
> <h3>Java (GCJ)</h3>
> + <ul>
> + <li>Java now enable unit-at-a-time compilation by default. This enables
> + more aggressive optimization, in particular inlining decisions. The
> + memory consumption of compiling large <code>jar</code> archives might
> + grow and require splitting those archives to smaller units.</li>
> + </ul>
"Java now uses..." (since we have enable in the next sentence). And is
this really just "by default" or in general, in which case I recommend
to simply omit the "by default" part.
"into smaller units", I believe.
Thanks,
Gerald