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: Toplevel bootstrap only - where are we?

From: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
To: Daniel Jacobowitz <drow at false dot org>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Mon, 30 Jan 2006 16:00:53 +0100
Subject: Re: Toplevel bootstrap only - where are we?
References: <10601301454.AA10925@vlsi1.ultra.nyu.edu> <20060130145303.GA10219@nevyn.them.org>

Daniel Jacobowitz wrote:

On Mon, Jan 30, 2006 at 09:54:44AM -0500, Richard Kenner wrote:

I'm sending this just to you to avoid breaking the thread at a particularly
bad spot.

   So, how many people are still working with old-style GCC subdirectory
   bootstrap?  What blockers are there, besides retraining our fingers?

It would help me greatly, and I suspect others too, if you or somebody
else could say precisely what the differences are (other than
"retraining our fingers").  Specifically, are there things we can do now
that we couldn't in the new scheme?

There are too many now/new for me to understand the sentence.

If you mean "with the patches I sent this morning", yes. You can: 1) type "make cc1plus" in the stage1 gcc compiler to build a stage1 C++ compiler; 2) type "make all-gcc" after configure to build stage1 up to gcc (or type "make all-gcc" to build the current stage up to gcc with all the dependencies); 3) type "make quickstrap" in the GCC directory and be sure that you are not triggering a whole lot of unwanted builds. The rest are bugfixes.

Also, this can be an occasion to point out that the toplevel libgcc is a prerequisite to show the stageN-gcc directory name in the compilation commands.

How much more is being compiled in a bootstrap with the new scheme than the old?

Everything that used to be compiled for the host machine before gcc, is now compiled three times.

Paolo's really the man to answer that, CC'd. Don't suppose it's in the just-submitted texinfo docs?

I think it is.

Also, of course, the "retraining" is a bit of a misnomer, since many people still have to work in both old and new directories ...

Of course - most of us, even.

Well, I'm lucky that I rarely debug native 3.4/4.0/4.1 -- I just backport 4.2 patches and let the bootstrap run overnight (with scripts). I suspect I'm not alone.

Paolo

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