This is the mail archive of the gcc@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]
Other format: [Raw text]

Re: [buildrobot] microblaze-elf / microblaze-linux


On 11/25/13 19:26, Jan-Benedict Glaw wrote:
Hi!

Build logs at
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=39192
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=40718

(I also think that we'd have the little endian version on the target
list at contrib/config-list.mk ...)


g++ -c   -g -O2 -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE  -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common  -DHAVE_CONFIG_H -I. -I. -I../../../gcc/gcc -I../../../gcc/gcc/. -I../../../gcc/gcc/../include -I../../../gcc/gcc/../libcpp/include -I/opt/cfarm/mpc/include  -I../../../gcc/gcc/../libdecnumber -I../../../gcc/gcc/../libdecnumber/dpd -I../libdecnumber -I../../../gcc/gcc/../libbacktrace    -o reload1.o -MT reload1.o -MMD -MP -MF ./.deps/reload1.TPo ../../../gcc/gcc/reload1.c
../../../gcc/gcc/reload1.c: In function âvoid elimination_costs_in_insn(rtx)â:
../../../gcc/gcc/reload1.c:3750:41: error: âorig_dup[0]â may be used uninitialized in this function [-Werror=maybe-uninitialized]
      *recog_data.dup_loc[i] = orig_dup[i];
                                          ^
cc1plus: all warnings being treated as errors
make[2]: *** [reload1.o] Error 1

I do not see this error in my build of microblaze-elf.

I notice that there are flags in your compile that do not appear in mine:
-pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror

I don't see any warnings in my build, either.

My build is using gcc-4.1.2 (on CentOS 5.9) as a build compiler.  My
guess is that this is the cause of the differences.

I'll upgrade to building with a more recent version of gcc and investigate
this failure, but I won't be able to look at this for about two weeks.

--
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


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