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: Richard Guenther <richard dot guenther at gmail dot com>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 16 Jan 2006 19:23:26 +0100
- Subject: Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)
- References: <10601161824.AA12482@vlsi1.ultra.nyu.edu>
On 1/16/06, Richard Kenner <kenner@vlsi1.ultra.nyu.edu> wrote:
>
> I never tried to "bootstrap" on x86_64 using --host=i686 --target=i686
> to build a 32bit compiler building 32bit
>
> Well, that's my point. It's not really a bootstrap. First you use the
> cross-compiler to build a native compiler and *then* you bootstrap.
The question what is "native" here remains - on a biarch platform I can
run both 32bit and 64bit executables. So the argument is we can
"stretch" the definition of a bootstrap or a native compiler a bit in allowing
all 32bit/64bit combinations as native configurations rather than
cross-compilers.
config.guess of course just uses uname to decide what the host environment is,
and uname does not know anything about bi-archness.
Richard.