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 wrote:

Paolo Bonzini <paolo.bonzini@lu.unisi.ch> writes:

| And at last,

Hi Paolo,

 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?

It's pretty hard; basically the debugging information for the fixincluded headers shows up as comparison failures, if you try to do anything like that.

I'd like to fix this after Dan's toplevel libgcc goes in. It would be a big improvement in general, for example you could do two `make check' runs for two different stages at the same time, or just run make in stageN-gcc.

For now, if you are logging the compilation process (e.g. with nohup), you can grep it for ^Configuring.

Paolo


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