public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/55571] [4.6/4.7/4.8 regression] PR48076 fix broke bootstrap on armv5tel-linux-gnueabi
Date: Mon, 03 Dec 2012 14:43:00 -0000 [thread overview]
Message-ID: <bug-55571-4-vmVPTvVCfo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55571-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55571
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |4.7.3, 4.8.0
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-12-03 14:43:13 UTC ---
> Eric has already "upgraded" this bug report to a 4.6/4.7/4.8 regression, but
> I'd like to add that I now got a very similar error with 4.8-20121202:
Sure, our 4.7.x arm-linux-gnueabi cross-compiler is also affected.
next prev parent reply other threads:[~2012-12-03 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 8:42 [Bug bootstrap/55571] New: [4.6.4 " mikpe at it dot uu.se
2012-12-03 9:23 ` [Bug bootstrap/55571] [4.6/4.7/4.8 " ebotcazou at gcc dot gnu.org
2012-12-03 11:37 ` rguenth at gcc dot gnu.org
2012-12-03 13:55 ` jakub at gcc dot gnu.org
2012-12-03 14:39 ` mikpe at it dot uu.se
2012-12-03 14:43 ` ebotcazou at gcc dot gnu.org [this message]
2012-12-03 15:34 ` rth at gcc dot gnu.org
2012-12-03 16:49 ` rth at gcc dot gnu.org
2012-12-03 16:49 ` rth at gcc dot gnu.org
2012-12-03 19:04 ` rth at gcc dot gnu.org
2012-12-04 4:52 ` brobecker at gnat dot com
2012-12-04 17:09 ` rth at gcc dot gnu.org
2012-12-04 19:06 ` rth at gcc dot gnu.org
2012-12-04 19:08 ` rth at gcc dot gnu.org
2012-12-04 19:10 ` rth at gcc dot gnu.org
2012-12-04 19:11 ` rth at gcc dot gnu.org
2012-12-04 19:13 ` rth at gcc dot gnu.org
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=bug-55571-4-vmVPTvVCfo@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).