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: [PATCH] toplevel bootstrap documentation


Gabriel Dos Reis <gdr@integrable-solutions.net> writes:

>   With the old machinery, it was possible, with a visual inspection of
> the compilation process, at what stage was the bootstrap because there
> was something like /path/to/stageN/xgcc in the commands.  Something
> that seems to have disappear now.  Is there a way to have similar
> effect, e.g. a visual marker?

There's more about this than just a visual marker: with the old bootstrap,
you could just cut-and-paste the compilation commands from a build log to
rebuild a specific stage2 or stage3 file, possibly with more compiler flags
(like -g3 -save-temps) added to investigate e.g. comparision failures.
This is now much harder to do: you have to move around the prev-gcc or
stage1-gcc directories or manually fix the command lines.

	Rainer


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