public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46221] [4.6 Regression] huge number of c++ testsuite failures, libstdc++.so alias missing
Date: Wed, 15 Dec 2010 16:28:00 -0000 [thread overview]
Message-ID: <bug-46221-4-jOfhksAyEw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46221-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46221
Dave Korn <davek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc-linux, i?86-linux, |powerpc-linux, i?86-linux,
|alpha-linux |alpha-linux, i?86-pc-cygwin
Status|RESOLVED |REOPENED
CC| |davek at gcc dot gnu.org
Depends on| |46674
Resolution|FIXED |
AssignedTo|rguenth at gcc dot gnu.org |davek at gcc dot gnu.org
--- Comment #26 from Dave Korn <davek at gcc dot gnu.org> 2010-12-15 16:28:12 UTC ---
(In reply to comment #25)
> *** Bug 46674 has been marked as a duplicate of this bug. ***
Actually, it's a genuine bug in the patch; it ends up comparing C identifiers
to actual assembler names, which works fine when there's no USER_LABEL_PREFIX
and when none of the nodes in question have __asm("..") names, but runs into
problems if/when there is/they do.
See attachment 22765 for the patch to resolve all this by always using
assembler names. Bootstraps and testruns are under way.
next prev parent reply other threads:[~2010-12-15 16:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 5:32 [Bug c++/46221] New: " amodra at gmail dot com
2010-10-29 5:39 ` [Bug c++/46221] " amodra at gmail dot com
2010-10-29 5:40 ` amodra at gmail dot com
2010-10-29 13:01 ` amodra at gmail dot com
2010-10-30 4:37 ` amodra at gmail dot com
2010-10-30 4:42 ` amodra at gmail dot com
2010-10-30 8:36 ` amodra at gmail dot com
2010-11-01 19:21 ` meissner at gcc dot gnu.org
2010-11-03 21:30 ` [Bug middle-end/46221] [4.6 Regression] " rguenth at gcc dot gnu.org
2010-11-03 21:37 ` rguenth at gcc dot gnu.org
2010-11-06 7:44 ` ubizjak at gmail dot com
2010-11-08 11:55 ` rguenth at gcc dot gnu.org
2010-11-08 12:03 ` rguenth at gcc dot gnu.org
2010-11-08 13:32 ` rguenth at gcc dot gnu.org
2010-11-08 14:19 ` rguenth at gcc dot gnu.org
2010-11-08 14:37 ` bergner at gcc dot gnu.org
2010-11-08 20:13 ` hubicka at ucw dot cz
2010-11-08 22:20 ` ubizjak at gmail dot com
2010-11-09 1:51 ` bergner at gcc dot gnu.org
2010-11-09 10:37 ` rguenth at gcc dot gnu.org
2010-11-09 10:37 ` rguenth at gcc dot gnu.org
2010-11-10 5:12 ` howarth at nitro dot med.uc.edu
2010-11-10 10:26 ` rguenther at suse dot de
2010-11-10 13:32 ` bergner at gcc dot gnu.org
2010-11-10 13:39 ` rguenther at suse dot de
2010-11-10 13:58 ` bergner at gcc dot gnu.org
2010-11-27 18:38 ` pinskia at gcc dot gnu.org
2010-12-15 16:28 ` davek at gcc dot gnu.org [this message]
2010-12-19 11:15 ` davek at gcc dot gnu.org
2010-12-19 11:19 ` davek 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-46221-4-jOfhksAyEw@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).