This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bootstrap failure on ppc64
Tim Prince <n8tm@aol.com> writes:
> ERES@il.ibm.com wrote:
> > ../../gcc/libcpp/traditional.c: In function Ã_cpp_scan_out_logical_lineÃ:
> > ../../gcc/libcpp/traditional.c:349: error: Ãfmacro.argsà may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: Ãfmacro.nodeà may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: Ãfmacro.offsetà may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: Ãfmacro.argcà may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: Ãfmacro.lineà may be used
> > uninitialized in this function
> > make[3]: *** [traditional.o] Error 1
> > make[3]: Leaving directory `/home/eres/mainline_lim/build/libcpp'
> > make[2]: *** [all-stage2-libcpp] Error 2
> > make[2]: Leaving directory `/home/eres/mainline_lim/build'
> > make[1]: *** [stage2-bubble] Error 2
> > make[1]: Leaving directory `/home/eres/mainline_lim/build'
> > make: *** [bootstrap] Error 2
> So it looks like you must remove the -Werror option. Several of the
> Makefile.in files have WERROR macros which can be nulled out to avoid
> setting -Werror.
No, please initialize the fields in fmacro instead. The warning is
probably wrong but the cost of adding an explicit initialization is
low.
Ian