This is the mail archive of the gcc-bugs@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]

Re: Bootstrap failure in stage1 fix-header, !HAVE_DESIGNATED_INITIALIZERS


 > 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.

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions

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