public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: oliver.kellogg@t-online.de (Oliver Kellogg)
To: gcc@gcc.gnu.org
Subject: mainline breakage (r148442)
Date: Sun, 14 Jun 2009 03:43:00 -0000	[thread overview]
Message-ID: <1244951419.5945.2.camel@tidbit.site> (raw)

Anybody else seeing this?

/usr/src/packages/BUILD/build-gcc-orig/./prev-gcc/xgcc
-B/usr/src/packages/BUILD/build-gcc-orig/./prev-gcc/
-B/opt/gnat/fsf/i686-pc-linux-gnu/bin/
-B/opt/gnat/fsf/i686-pc-linux-gnu/bin/
-B/opt/gnat/fsf/i686-pc-linux-gnu/lib/
-isystem /opt/gnat/fsf/i686-pc-linux-gnu/include
-isystem /opt/gnat/fsf/i686-pc-linux-gnu/sys-include    -c  -g
-fomit-frame-pointer -DIN_GCC   -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wcast-qual
-Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror
-fno-common  -DHAVE_CONFIG_H -I. -I. -I../../../SOURCES/gcc/gcc
-I../../../SOURCES/gcc/gcc/. -I../../../SOURCES/gcc/gcc/../include
-I../../../SOURCES/gcc/gcc/../libcpp/include
-I../../../SOURCES/gcc/gcc/../libdecnumber
-I../../../SOURCES/gcc/gcc/../libdecnumber/bid
-I../libdecnumber    ../../../SOURCES/gcc/gcc/tree-eh.c -o tree-eh.o
cc1: warnings being treated as errors
../../../SOURCES/gcc/gcc/tree-eh.c: In function
‘lower_try_finally_switch’:
../../../SOURCES/gcc/gcc/tree-eh.c:1350:5: error: ‘tf_loc’ may be used
uninitialized in this function
make[3]: *** [tree-eh.o] Error 1
make[3]: Leaving directory `/usr/src/packages/BUILD/build-gcc-orig/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory `/usr/src/packages/BUILD/build-gcc-orig'
make[1]: *** [stage2-bubble] Error 2


             reply	other threads:[~2009-06-14  3:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14  3:43 Oliver Kellogg [this message]
2009-06-15 13:50 ` Aldy Hernandez

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=1244951419.5945.2.camel@tidbit.site \
    --to=oliver.kellogg@t-online.de \
    --cc=gcc@gcc.gnu.org \
    --cc=okellogg@users.sourceforge.net \
    /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).