This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Bootstrap failure in stage1 fix-header, !HAVE_DESIGNATED_INITIALIZERS
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: Bootstrap failure in stage1 fix-header, !HAVE_DESIGNATED_INITIALIZERS
- From: Zack Weinberg <zack at wolery dot cumb dot org>
- Date: Sun, 20 Aug 2000 10:16:40 -0700
- Cc: NeilB at earthling dot net, gcc-bugs at gcc dot gnu dot org
- References: <200008201616.MAA20103@caip.rutgers.edu>
On Sun, Aug 20, 2000 at 12:16:10PM -0400, Kaveh R. Ghazi wrote:
> > From: Neil Booth <NeilB@earthling.net>
> >
> > Zack Weinberg wrote:-
> >
> > > Argh. Right. Add a call to cpp_init() just before the call to
> > > cpp_reader_init(&scan_in) in fix-header.c:read_scan_file. That should
> > > fix the problem. (If it does, please check in a patch to that effect.)
> >
> > OK, I've done this.
> >
> > Neil.
> >
> > * fix-header.c (main): Initialize cpplib.
>
>
> Thanks, my bootstraps have managed to enter stage2 so this problem
> appears to be fixed.
>
> IMHO, it would be useful to include an assertion somewhere in the
> cpplib code (perhaps wrapped by ENABLE_CHECKING) that ensures cpp_init
> has been called even if designated initializers are available. That
> way one can catch this problem even if they are using gcc.
Good idea. I'll add something to that effect.
zw