On Fri, 2014-09-19 22:26:59 +0200, Jan-Benedict Glaw <jbg...@lug-owl.de> wrote:
> On Thu, 2014-09-18 16:55:35 -0500, Joel Sherrill <joel.sherr...@oarcorp.com> 
> wrote:
> > I only see one RTEMS target that has been built in the top page.
> > Are more than the powerpc-rtems being built? How can I check?
> 
> The builders work down their list, and when done will start a new
> round (with a list that would now contain the three new targets.)
> Though they're still working down their "old" list; I've just added
> the targets there as well, they should show up soonish on one of the
> *-configlist_mk* builders.

Here we are:

arm-rtems was successfully built
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=355716

powerpc-rtems was successfully built
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=355861

nios2-rtems failed to build
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=355729

Please note that nios2 failed in the same way a number of other
targets fail, too:

cr16-elf
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=351532
fr30-elf
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=348510
lm32-elf
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=352224
microblaze-elf
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=347412
moxie-elf
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=355056
rl78-elf
        http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=355368

The build error always looks like this (I should have opened a PR for
that already, but didn't):

[...]
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 -Woverloaded-virtual -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_insn*)’:
../../../gcc/gcc/reload1.c:3762: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


(All config-list.mk builds are done with a compiler of the very same
revision number.)


MfG, JBG

-- 
      Jan-Benedict Glaw      jbg...@lug-owl.de              +49-172-7608481
 Signature of:                      http://perl.plover.com/Questions.html
 the second  :

Attachment: signature.asc
Description: Digital signature

Reply via email to