This is the mail archive of the
gcc-regression@gcc.gnu.org
mailing list for the GCC project.
Re: GCC build failed for native with your patch on 2004-01-27T03:45:02Z.
- From: Geoff Keating <geoffk at desire dot geoffk dot org>
- To: pinskia at physics dot uc dot edu
- Cc: pinskia at physics dot uc dot edu, ro at TechFak dot Uni-Bielefeld dot DE, fjahanian at apple dot com, rth at redhat dot com, ghazi at caip dot rutgers dot edu, jh at suse dot cz, law at redhat dot com, mark at codesourcery dot com, pcarlini at suse dot de, ian at wasabisystems dot com, kazu at cs dot umass dot edu, gcc-regression at gcc dot gnu dot org
- Date: Wed, 28 Jan 2004 00:05:55 -0800
- Subject: Re: GCC build failed for native with your patch on 2004-01-27T03:45:02Z.
- References: <20040127040331.928DBBD51DB4@gcc-regress.apple.com> <jmfze1kv68.fsf@desire.geoffk.org> <20040127211256.GL28740@kam.mff.cuni.cz> <jm4quglv95.fsf@desire.geoffk.org> <AFCB6401-5154-11D8-B070-000393A6D2F2@physics.uc.edu>
> From: Andrew Pinski <pinskia@physics.uc.edu>
> Date: Tue, 27 Jan 2004 21:41:57 -0800
> On Jan 27, 2004, at 17:25, Geoff Keating wrote:
> >>
> >> This looks somewhat strange, as the pattern must be refused by recog
> >> that is called several times without clearing the arrays and definitly
> >> shall not depend on it. Can I have testcase?
> >
> > I've been tracking it back, and at the moment it looks like it's
> > caused by:
> >
> > /Users/regress/tbox/cvs-gcc/gcc/gcc/read-rtl.c:718: warning: implicit
> > declaration of function `atoll'
> >
> > which is of course fatal, it fails to read the '1' in from the .md
> > file correctly. But (this is the neat part) this warning does not
> > happen when I run the same command, running the system gcc, by
> > hand, and I can see that there is indeed an atoll declaration in
> > stdlib.h.
>
>
> This sounds like your header files were not updated at all as 10.2 did
> not have atoll at all.
> while 10.3 does. On my machine it runs just fine which has the correct
> headers.
My headers were updated, but it turns out the tester wasn't using the
system gcc, it was using the one that build-objs.sh made, which runs
fixincludes as it installs. Fortunately, we have mkheaders now, so I
can just run that and hopefully the tester will be fine again.
--
- Geoffrey Keating <geoffk@geoffk.org>