public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mrs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/54625] [4.8 Regression] lto/profiledbootstrap broken by r191466: ICE: in cgraph_clone_edge, at cgraphclones.c:123
Date: Tue, 15 Oct 2013 00:02:00 -0000 [thread overview]
Message-ID: <bug-54625-4-ExHfGV4r2I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54625-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54625
mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mrs at gcc dot gnu.org
--- Comment #10 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> ---
xgcc: error: /home/mrs/wg/gcc/gcc/testsuite/gcc.dg/lto/pr54625-2_1.C: C++
compiler not installed on this system^M
FAIL: gcc.dg/lto/pr54625-2 c_lto_pr54625-2_1.o assemble, -O2 -flto
-fuse-linker-plugin
shouldn't C++ testcases go into the C++ testsuite?
prev parent reply other threads:[~2013-10-15 0:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 11:21 [Bug lto/54625] New: [4.8 Regression] lto/profiledbootstrap broken markus at trippelsdorf dot de
2012-09-19 11:40 ` [Bug lto/54625] " rguenth at gcc dot gnu.org
2012-09-19 14:31 ` markus at trippelsdorf dot de
2012-09-22 4:38 ` markus at trippelsdorf dot de
2012-09-22 8:08 ` markus at trippelsdorf dot de
2012-09-25 13:17 ` [Bug lto/54625] [4.8 Regression] lto/profiledbootstrap broken by r191466: ICE: in cgraph_clone_edge, at cgraphclones.c:123 rguenth at gcc dot gnu.org
2012-09-25 13:23 ` rguenth at gcc dot gnu.org
2012-09-25 13:28 ` rguenth at gcc dot gnu.org
2012-09-25 14:25 ` markus at trippelsdorf dot de
2012-09-25 15:07 ` rguenth at gcc dot gnu.org
2012-09-25 15:08 ` rguenth at gcc dot gnu.org
2013-10-15 0:02 ` mrs at gcc dot gnu.org [this message]
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-54625-4-ExHfGV4r2I@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).