public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/52297] FAIL: gcc.dg/lto/trans-mem-1 c_lto_trans-mem-1_0.o-c_lto_trans-mem-1_1.o link, -flto -fgnu-tm
Date: Fri, 17 Feb 2012 16:00:00 -0000 [thread overview]
Message-ID: <bug-52297-4-kJY8FGdDqB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52297-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52297
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-02-17
CC| |ebotcazou at gcc dot
| |gnu.org
Ever Confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-02-17 15:45:29 UTC ---
AFAICT this affects also most of (all?) the *-linux-* platforms,e.g.,
http://glutton.geoffk.org/HEAD/native-logsum/gcc/testsuite/gcc/gcc.log.gzip.
The failures appeared between revisions 184169 and 184177 (see
http://gcc.gnu.org/ml/gcc-regression/2012-02/msg00077.html and
http://gcc.gnu.org/ml/gcc-regression/2012-02/msg00071.html), likely revision
184174.
next prev parent reply other threads:[~2012-02-17 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 14:56 [Bug driver/52297] New: " danglin at gcc dot gnu.org
2012-02-17 16:00 ` dominiq at lps dot ens.fr [this message]
2012-02-20 12:20 ` [Bug testsuite/52297] [4.7 Regression] " rguenth at gcc dot gnu.org
2012-02-20 13:29 ` dominiq at lps dot ens.fr
2012-02-21 10:16 ` ebotcazou at gcc dot gnu.org
2012-02-22 10:10 ` jakub at gcc dot gnu.org
2012-02-22 20:09 ` aldyh at gcc dot gnu.org
2012-02-22 20:21 ` jakub at gcc dot gnu.org
2012-02-22 21:03 ` aldyh at redhat dot com
2012-02-23 17:58 ` ebotcazou at gcc dot gnu.org
2012-02-29 10:07 ` rguenth at gcc dot gnu.org
2012-02-29 10:13 ` rguenth 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-52297-4-kJY8FGdDqB@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).