make profiledbootstrap

[Fergus Henderson]

I have some suggestions about minor wording issues in the documentation.

On 22-Feb-2003, Jan Hubicka <jh@suse.cz> wrote:
> + @section Building with profile feedback
> + 
> + It is possible to use profile feedback to optimize compiler itself.  This

s/compiler/the compiler/

> + should result in faster compiler binary.  Experiments done on x86 using gcc 3.3

s/faster/a faster/

> + did show approximately 7 percent speedup on compiling C programs.

s/did show/showed/

> + Using @samp{make profiledbootstrap} first @code{stage1} compiler is built.

I suggest

When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
compiler.

> + This compiler is used to build @code{stagefeedback} compiler instrumented to

s/build/build a/

> + collect execution counts of instruction and branch probabilities.  Then runtime
> + libraries are copiled with profile collected.  Finally @code{stageprofile}

s/copiled/compiled/
s/Finally/Finally a/

> + compiler is built using the infromation collected.

s/infromation/information/

> + Unlike @samp{make bootstrap} several additional restriction apply.  The

s/restriction/restrictions/

> + compiler used to build @code{stage1} needs to support 64bit type.  It is

s/64bit type/a 64-bit integral type/

> + recommended to only use GCC for this.  Also the parallel make is currently not
> + supported since collisions in profile collecting may occur.

s/the parallel make/parallel make/

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.