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 lto/63409] [5 Regression] FAIL: g++.dg/lto/pr63270 cp_lto_pr63270_0.o-cp_lto_pr63270_1.o link, -flto -O2 -Wno-odr -fno-linker-plugin
Date: Tue, 30 Sep 2014 10:46:00 -0000 [thread overview]
Message-ID: <bug-63409-4-AEFr1vn4t7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63409-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63409
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-09-30
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I get the same failure on x86_64-apple-darwin13 configured with
../work/configure --prefix=/opt/gcc/gcc4.10w
--enable-languages=c,c++,fortran,objc,obj-c++,ada,java,lto --with-gmp=/opt/mp
--with-system-zlib --with-isl=/opt/mp --enable-lto --enable-plugin
--with-arch=corei7 --with-cpu=corei7
and tested with
make -k check RUNTESTFLAGS="--target_board=unix'{-m32,-m64}'"
AFAICT the test (r215451) never passed.
next prev parent reply other threads:[~2014-09-30 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 15:58 [Bug lto/63409] New: " ubizjak at gmail dot com
2014-09-30 10:18 ` [Bug lto/63409] " rguenth at gcc dot gnu.org
2014-09-30 10:46 ` dominiq at lps dot ens.fr [this message]
2014-09-30 11:10 ` mliska at suse dot cz
2014-10-03 13:33 ` ubizjak at gmail dot com
2014-10-06 14:33 ` ro at gcc dot gnu.org
2014-10-06 16:18 ` mliska at suse dot cz
2014-10-07 6:45 ` ubizjak at gmail dot com
2014-10-07 8:28 ` mliska at suse dot cz
2014-10-07 11:01 ` 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-63409-4-AEFr1vn4t7@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).