This is the mail archive of the gcc@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: 4.3 build failure in driver-i386.c

From: Andreas Schwab <schwab at suse dot de>
To: "Richard Guenther" <richard dot guenther at gmail dot com>
Cc: "Greg Schafer" <gschafer at zip dot com dot au>, gcc at gcc dot gnu dot org, "Rask Ingemann Lambertsen" <rask at sygehus dot dk>
Date: Sun, 17 Feb 2008 10:54:50 +0100
Subject: Re: 4.3 build failure in driver-i386.c
References: <pan.2008.02.17.08.38.49.138928@zip.com.au> <84fc9c000802170140x56e3c9d9nae9386deb8c449ac@mail.gmail.com> <84fc9c000802170143p48b1a34bw82664589768c27fc@mail.gmail.com>

"Richard Guenther" <richard.guenther@gmail.com> writes:

> I see the use of cpuid.h is wrapped inside #ifdef __GNUC__, so the issue is only
> using old GCC as the host compiler (I checked 2.95 which chokes on the asm).
> Can we change this guard to only allow GCC >= 3.3 which would also fix this?

Won't those host dependent parameters cause bootstrap comparison
failures?  If the stage1 compiler doesn't use the same detection
routines as the stage2 compiler then the stage2 compiler is compiled
with different options than the stage3 compiler.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: 4.3 build failure in driver-i386.c
  - From: Richard Guenther

References:
- 4.3 build failure in driver-i386.c
  - From: Greg Schafer
- Re: 4.3 build failure in driver-i386.c
  - From: Richard Guenther
- Re: 4.3 build failure in driver-i386.c
  - From: Richard Guenther

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