This is the mail archive of the 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] Fix PR42843 to use built compilers

Joern Rennecke <> writes:

> Quoting Jack Howarth <>:
>>   The previous fix for PR testsuite/42843 (r160461) incorrectly
>> set PLUGINCC and PLUGINCFLAGS to the values for the host
>> compiler rather than the built compiler.
> Actually, it's the build compiler vs. built (target) compiler.
> And using the build compiler is right in the non-bootstrap case.
> Even in the boostrap case, it only makes a difference if there
> is an incompatibly between the build compiler and the stage2/
> stage3 AKA target compiler.

... which is likely to be the case.  The problem is biggest if you
bootstrap with some vendor compiler, but I've also observed the problem
when bootstrapping on Solaris 8 and 9 with GCC 4.4: while 4.5 and
mainline provide their own <stdint.h>, GCC 4.4 does not and the host OS
lacks it, so all plugin tests fail.  Even if you add
-I$(objdir)/gcc/include to fetch the mainline-provided file, this
doesn't work because it references macros like __INT_LEAST8_TYPE__ that
aren't defined by pre-4.5 GCCs.  One could instead use the stage1
headers where configure was run with the build compiler, but that breaks
down with make bootstrap-lean.

Your change for PR testsuite/42843 introduced a regression from 4.5.


Rainer Orth, Center for Biotechnology, Bielefeld University

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