public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Joel Sherrill <Joel.Sherrill@OARcorp.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, Michael Eager <eager@eagercon.com>
Subject: Re: [buildrobot] microblaze-elf / microblaze-linux
Date: Tue, 26 Nov 2013 14:51:00 -0000	[thread overview]
Message-ID: <20131126145119.GQ30563@lug-owl.de> (raw)
In-Reply-To: <1djbjk1n62mkaiqxbjm4lo51.1385469317186@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]

On Tue, 2013-11-26 06:33:39 -0600, Joel Sherrill <Joel.Sherrill@OARcorp.com> wrote:
> Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > 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
> > 
> Was microblaze-rtems attempted? I would have expected a failure like
> these if so.

No, it wasn't.  It's not on the list of targets in
.../gcc/contrib/config-list.mk .  So we'd probably add that to the
target list I guess?  I'll propose a patch later tonight (adding to
another pending patch to config-list.mk)

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:                   ...und wenn Du denkst, es geht nicht mehr,
the second  :                          kommt irgendwo ein Lichtlein her.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-11-26 14:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 12:35 Joel Sherrill
2013-11-26 14:51 ` Jan-Benedict Glaw [this message]
2013-11-26 15:21   ` Joern Rennecke
2013-11-26 15:28     ` Jan-Benedict Glaw
2013-11-26 16:03       ` Michael Eager
2013-11-26 16:52       ` Joseph S. Myers
2013-11-26 17:38         ` Joel Sherrill
2013-11-26 18:00           ` Ralf Corsepius
2013-11-26 18:54             ` Joel Sherrill
2013-11-26 19:50           ` Joern Rennecke
2013-11-26 19:54             ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2013-11-26  3:20 [buildrobot] First results of running contrib/config-list.mk Jan-Benedict Glaw
2013-11-26  3:27 ` [buildrobot] microblaze-elf / microblaze-linux Jan-Benedict Glaw
2013-11-26 15:51   ` Michael Eager
2013-11-26 16:08     ` Jan-Benedict Glaw
2013-11-26 16:13       ` Michael Eager
2013-11-26 16:17         ` Jan-Benedict Glaw
2013-11-26 17:16           ` Michael Eager

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131126145119.GQ30563@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=Joel.Sherrill@OARcorp.com \
    --cc=eager@eagercon.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).