public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/60984] [4.9 Regression] AIX: gcc-4.9.0 bootstrap fails in stage-2
Date: Tue, 20 May 2014 23:23:00 -0000	[thread overview]
Message-ID: <bug-60984-4-Km3JfSk0qc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60984-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #26 from Jan Hubicka <hubicka at ucw dot cz> ---
> Thanks for tracking this down. I will test it as well. AIX is a very good
> canary for these types of bugs.

Yeah, the difference here is that we produce a lot more local aliases on AIX
than elsewhere.  We discussed it previously - it is because middle-end believes
that comdat mechanizm is missing and only WEAK is used. If AIX linker has
mechanizm to throw away unused comdat functions, we ought to model this to the
middle-end. (perhaps something like unreachable_symbol_removal_in_linker target
hook or so)

Honza


  parent reply	other threads:[~2014-05-20 23:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  9:05 [Bug bootstrap/60984] New: " tgard at opentext dot com
2014-04-28 13:46 ` [Bug bootstrap/60984] " dje at gcc dot gnu.org
2014-04-28 19:23 ` dje at gcc dot gnu.org
2014-04-28 19:41 ` dje at gcc dot gnu.org
2014-04-28 22:09 ` dje at gcc dot gnu.org
2014-04-29  7:49 ` jakub at gcc dot gnu.org
2014-04-29  7:55 ` [Bug bootstrap/60984] [4.9 Regression] " rguenth at gcc dot gnu.org
2014-04-29 12:54 ` dje at gcc dot gnu.org
2014-04-29 14:11 ` tgard at opentext dot com
2014-04-29 17:01 ` dje at gcc dot gnu.org
2014-04-29 17:56 ` dje at gcc dot gnu.org
2014-05-02  7:59 ` tgard at opentext dot com
2014-05-02 13:29 ` tgard at opentext dot com
2014-05-04 20:13 ` dje at gcc dot gnu.org
2014-05-05  7:18 ` tgard at opentext dot com
2014-05-05 15:25 ` tgard at opentext dot com
2014-05-08  1:18 ` dje at gcc dot gnu.org
2014-05-08  2:05 ` dje at gcc dot gnu.org
2014-05-08  3:00 ` dje at gcc dot gnu.org
2014-05-08 17:42 ` dje at gcc dot gnu.org
2014-05-09 14:29 ` hubicka at gcc dot gnu.org
2014-05-09 15:44 ` dje at gcc dot gnu.org
2014-05-09 15:53 ` dje at gcc dot gnu.org
2014-05-10 14:57 ` dje at gcc dot gnu.org
2014-05-10 15:34 ` dje at gcc dot gnu.org
2014-05-20 22:48 ` hubicka at ucw dot cz
2014-05-20 23:02 ` dje at gcc dot gnu.org
2014-05-20 23:23 ` hubicka at ucw dot cz [this message]
2014-05-21  1:45 ` dje at gcc dot gnu.org
2014-05-21  5:40 ` hubicka at gcc dot gnu.org
2014-05-21  5:42 ` hubicka at gcc dot gnu.org
2014-05-21  5:45 ` hubicka at gcc dot gnu.org
2014-05-22 12:11 ` tgard at opentext dot com
2014-05-22 21:06 ` fbissey at slingshot dot co.nz

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-60984-4-Km3JfSk0qc@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).