public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jiez at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46674] [4.6 Regression] Weak alias is mistakenly optimized away
Date: Tue, 30 Nov 2010 10:01:00 -0000	[thread overview]
Message-ID: <bug-46674-4-Y7LRsPDNDx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46674-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46674

--- Comment #4 from Jie Zhang <jiez at gcc dot gnu.org> 2010-11-30 10:00:05 UTC ---
Hah, I now know the root cause. It's "*__GI_memchr" that is added into the
visible point set since it's a user provided name. But GCC looks for
"__GI_memchr" later, which is not the same identifier as "*__GI_memchr". Is
there a way to easily translate a "*__GI_memchr" identifier to a "__GI_memchr"
one?


  parent reply	other threads:[~2010-11-30 10:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 12:28 [Bug middle-end/46674] New: Weak alias was " jiez at gcc dot gnu.org
2010-11-26 12:43 ` [Bug middle-end/46674] [4.6 Regression] Weak alias is " rguenth at gcc dot gnu.org
2010-11-27 18:34 ` pinskia at gcc dot gnu.org
2010-11-29  5:15 ` jiez at gcc dot gnu.org
2010-11-29 11:05 ` jiez at gcc dot gnu.org
2010-11-30 10:01 ` jiez at gcc dot gnu.org [this message]
2010-11-30 12:08 ` jiez at gcc dot gnu.org
2010-12-02  4:10 ` jiez at gcc dot gnu.org
2010-12-06 12:21 ` jakub at gcc dot gnu.org
2010-12-07  4:31 ` davek at gcc dot gnu.org
2010-12-10 14:29 ` davek at gcc dot gnu.org
2010-12-10 14:57 ` davek at gcc dot gnu.org
2010-12-15 16:18 ` davek at gcc dot gnu.org
2010-12-19 11:15 ` davek at gcc dot gnu.org
2010-12-19 11:18 ` 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-46674-4-Y7LRsPDNDx@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).