This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: [doc patch] Update -funit-at-a-time docs, and fix typos


On Tue, 20 Apr 2004, Bonzini wrote:
> 2004-04-20  Paolo Bonzini  <bonzini@gnu.org>
>
> 	* doc/invoke.texi (Optimize Options): Refer to
> 	"unit-at-a-time mode" rather than "-funit-at-a-time"
> 	since -O2 enables it without requiring -f* options.
> 	Refer to -fprofile-generate and -fprofile-use
> 	correctly.  Move -funit-at-a-time among options
> 	enabled by -O.

I'd prefer one of the hacker guys like Honzo to review this as well,
but some comments, if you don't mind.

> Index: invoke.texi
> ===================================================================
> +the program.  At @option{-O2} or higher level, @emph{unit-at-a-time}

How about "@option{-O2} and above" or "Optimization levels @option{-O2}
and above" "imply @emph{unit-at-a-time} mode"?

> +mode will be enabled, which will allow the compiler to consider

"allows"

> +information gained from later functions in the file when compiling a
> +function.  Compiling multiple files at once to a single output file
> +in @emph{unit-at-a-time} mode will allow the compiler to use information

"allows"

> +@item -funit-at-a-time
> +@opindex funit-at-a-time
> +Parse the whole compilation unit before starting to produce code.
> +This allows some extra optimizations to take place but consumes
> +(in general) more memory, and does not work when the code uses
> +@code{asm} directives and requires their ordering to be preserved
> +with respect to functions.

"but consumes more memory (in general)"

Well, but it does work also with asm.  How about: "code using @code{asm}"
directives and requiring their... may break"?

Gerald


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