public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51252] FAIL: c-c++-common/tm/freq.c (internal compiler error)
Date: Fri, 16 Dec 2011 18:22:00 -0000 [thread overview]
Message-ID: <bug-51252-4-KNjZIPN35w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51252-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51252
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-12-16 18:04:23 UTC ---
> --- Comment #4 from Richard Henderson <rth at gcc dot gnu.org> 2011-12-16 18:00:43 UTC ---
> While that might solve the ICE, the clone table doesn't actually
> get registered, which is why that clone-1 test case still fails.
>
> You'll need to play with collect2 and all its magic symbols to
> get that to work.
Of course, you mentioned that already. Unfortunately, I didn't have
much time for gcc work lately and don't know when I get around to it.
The hack I posted is certainly better than tons of ICEs when trying to
keep track of testsuite failures.
Rainer
next prev parent reply other threads:[~2011-12-16 18:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 2:54 [Bug target/51252] New: " danglin at gcc dot gnu.org
2011-11-27 20:55 ` [Bug target/51252] " danglin at gcc dot gnu.org
2011-12-16 17:51 ` [Bug middle-end/51252] " ro at gcc dot gnu.org
2011-12-16 17:56 ` ro at gcc dot gnu.org
2011-12-16 18:05 ` rth at gcc dot gnu.org
2011-12-16 18:22 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-12-17 1:18 ` dave.anglin at bell dot net
2011-12-19 0:10 ` dave.anglin at bell dot net
2011-12-23 2:03 ` danglin at gcc dot gnu.org
2011-12-23 2:11 ` danglin at gcc dot gnu.org
2012-01-09 15:56 ` patrick.marlier at gmail dot com
2012-01-09 18:45 ` dave.anglin at bell dot net
2012-01-10 18:47 ` ro at gcc dot gnu.org
2012-03-22 8:59 ` rguenth at gcc dot gnu.org
2012-07-02 12:59 ` rguenth at gcc dot gnu.org
2015-02-13 0:25 ` rth 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-51252-4-KNjZIPN35w@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).