public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at dixie dot net.nz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63435] Bad code with weak vs localalias on AIX
Date: Sun, 05 Oct 2014 21:09:00 -0000	[thread overview]
Message-ID: <bug-63435-4-4wYge832bN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63435-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63435

--- Comment #4 from Andrew Dixie <gcc at dixie dot net.nz> ---
I tried gcc-5-20140928 snapshot

This snapshot doesn't generate a localalias for the testcase, and it generates
very few localalias symbols in general.

There was only one localalias symbol produced in the entire gcc build tree:
[1228]  m   0x0000041c         1     1    0x6b         0x0000    
._ZNKSt14error_category23default_error_conditionEi.localalias.7
[1492]  m   0x00000b30         2     1    0x6b         0x0000    
_ZNKSt14error_category23default_error_conditionEi.localalias.7
[1578]  m   0x00000c6c         2     1    0x6b         0x0000    
_ZNKSt14error_category23default_error_conditionEi.localalias.7

Maybe there is something else wrong with gcc-4.9 that is causing it to generate
localalias symbols too aggressively?

We forced symtab_node::noninterposable_alias to return NULL on AIX.  This
resolved all the failures we were seeing in our application testsuite.


  parent reply	other threads:[~2014-10-05 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 23:13 [Bug c/63435] New: " gcc at dixie dot net.nz
2014-10-01 23:17 ` [Bug c/63435] " gcc at dixie dot net.nz
2014-10-02 22:02 ` [Bug target/63435] " hubicka at ucw dot cz
2014-10-05 21:09 ` gcc at dixie dot net.nz [this message]
2014-10-06 19:01 ` hubicka at ucw dot cz
2021-07-18 21:21 ` pinskia 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-63435-4-4wYge832bN@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).