This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- To: paolo dot bonzini at lu dot unisi dot ch
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 16 Jan 06 08:23:40 EST
- Subject: Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)
From the user point of view it is a bad bug that you cannot bootstrap
a 64-bit compiler starting from a 32-bit one (because stage2 does not
find a 64-bit libiberty to use).
To me, "bootstrap" means that all three compilers are identical in
configuration, so I don't follow your example.
Except "cd gcc; make bootstrap" because the two methods *cannot* live
together in the same tree.
Since that's what I (and others, from the sound of it), need to do all the
time, it sounds like we'll keep using --disable-bootstrap forever.