public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/44255] [4.6 regression] gcc-4.6-20100522 bootstrap comparison failure on sparc64 and arm
Date: Wed, 26 May 2010 15:17:00 -0000 [thread overview]
Message-ID: <20100526151659.23044.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44255-7665@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from mikpe at it dot uu dot se 2010-05-26 15:16 -------
(In reply to comment #2)
> My ARM box is currently busy running another test, but as soon as that finishes
> I'll check if r159600 is also responsible for the ARM bootstrap failure.
It is, r159599 bootstraps on ARM, r159600 does not.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44255
next prev parent reply other threads:[~2010-05-26 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 15:43 [Bug bootstrap/44255] New: [4.6 regression] gcc-4.6-20100522 bootstrap comparison failure on sparc64 mikpe at it dot uu dot se
2010-05-23 20:07 ` [Bug bootstrap/44255] " rguenth at gcc dot gnu dot org
2010-05-23 21:09 ` [Bug bootstrap/44255] [4.6 regression] gcc-4.6-20100522 bootstrap comparison failure on sparc64 and arm mikpe at it dot uu dot se
2010-05-24 9:31 ` mikpe at it dot uu dot se
2010-05-24 11:46 ` iains at gcc dot gnu dot org
2010-05-24 16:16 ` mikpe at it dot uu dot se
2010-05-24 16:22 ` mikpe at it dot uu dot se
2010-05-24 22:24 ` mikpe at it dot uu dot se
2010-05-25 7:38 ` iains at gcc dot gnu dot org
2010-05-25 7:58 ` jakub at gcc dot gnu dot org
2010-05-25 13:27 ` rguenth at gcc dot gnu dot org
2010-05-26 15:17 ` mikpe at it dot uu dot se [this message]
2010-05-27 21:36 ` mikpe at it dot uu dot se
2010-05-27 22:09 ` jakub at gcc dot gnu dot org
2010-05-28 16:02 ` mikpe at it dot uu dot se
2010-05-31 7:20 ` mikpe at it dot uu dot se
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=20100526151659.23044.qmail@sourceware.org \
--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).