public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/52878] [4.8 regression] bootstrap failure: "MASK_LONG_DOUBLE_128" redefined
Date: Mon, 16 Apr 2012 07:14:00 -0000 [thread overview]
Message-ID: <bug-52878-4-v3DxDEnQRH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52878-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52878
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #4 from Mikael Pettersson <mikpe at it dot uu.se> 2012-04-16 07:13:09 UTC ---
Can someone please fix this bootstrap failure? It's now been three weeks that
trunk hasn't bootstrapped on sparc64-linux.
next prev parent reply other threads:[~2012-04-16 7:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 15:44 [Bug bootstrap/52878] New: sparc64 " jamborm at gcc dot gnu.org
2012-04-05 16:11 ` [Bug bootstrap/52878] " hjl.tools at gmail dot com
2012-04-06 6:38 ` [Bug bootstrap/52878] [4.8 regression] " ebotcazou at gcc dot gnu.org
2012-04-06 12:24 ` hjl.tools at gmail dot com
2012-04-16 7:14 ` mikpe at it dot uu.se [this message]
2012-04-18 16:42 ` mikpe at it dot uu.se
2012-04-18 17:24 ` ebotcazou at gcc dot gnu.org
2012-04-18 17:35 ` hjl.tools at gmail dot com
2012-04-18 21:01 ` ebotcazou at gcc dot gnu.org
2012-04-18 21:06 ` hjl.tools at gmail dot com
2012-04-18 21:19 ` ebotcazou at gcc dot gnu.org
2012-04-18 21:43 ` hjl.tools at gmail dot com
2012-04-19 0:14 ` hjl.tools at gmail dot com
2012-04-19 8:42 ` ebotcazou at gcc dot gnu.org
2012-04-19 17:18 ` hjl.tools at gmail dot com
2012-04-20 20:16 ` mikpe at it dot uu.se
2012-04-23 23:21 ` rth at gcc dot gnu.org
2012-04-23 23:33 ` hjl at gcc dot gnu.org
2012-05-26 13:49 ` ebotcazou 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-52878-4-v3DxDEnQRH@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).