This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: [3.3 branch] IA64 bootstrap failure
- From: "Zack Weinberg" <zack at codesourcery dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: Andreas Schwab <schwab at suse dot de>, gcc-patches at gcc dot gnu dot org, Eric Botcazou <ebotcazou at libertysurf dot fr>, gcc at gcc dot gnu dot org
- Date: Tue, 08 Jul 2003 15:00:01 -0700
- Subject: Re: PATCH: [3.3 branch] IA64 bootstrap failure
- References: <je4r1xuq2i.fsf@sykes.suse.de><200307081526.26404.ebotcazou@libertysurf.fr><jeel11t8h2.fsf@sykes.suse.de> <20030708143705.GA13718@lucon.org><20030708211142.GA19746@lucon.org> <20030708215647.GA20483@lucon.org>
"H. J. Lu" <hjl@lucon.org> writes:
>> in the generated insn-conditions.c. It means the stage1 compiler may
>> be different from the stage2 compiler, depending on what compiler is
>> used to bootstrap gcc. I think insn-conditions.c should be the same
>> regardless the compiler used to boostrap.
>>
>>
>
> I am testing this patch now.
>
>
> H.J.
>
> 2003-07-08 H.J. Lu <hongjiu.lu@intel.com>
>
> * aclocal.m4 (gcc_AC_BUILTIN_CONSTANT_P): New.
> * configure.in: Use it.
> * configure: Regenerated.
> * config.in: Likewise.
>
> * genconditions.c (write_header): Use __builtin_constant_p if
> HAVE_BUILTIN_CONSTANT_P is defined.
Rejected, even if it fixes the bug. Your autoconf test is wrong -
__builtin_constant_p existed all the way back to 2.7 or earlier, but
did not do what insn-conditions.c needs until 3.0.1 - and furthermore
this merely papers over the real bug, which is somewhere else.
zw