public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/65150] [5 Regression] r220875 causes bootstrap failure on x86_64 darwin Date: Tue, 24 Feb 2015 04:31:00 -0000 [thread overview] Message-ID: <bug-65150-4-75OgNJ15g3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65150-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65150 --- Comment #12 from Jan Hubicka <hubicka at gcc dot gnu.org> --- The functions ought to be equivalent, so transfering just some users should not cause correctness issues. Of course unless the function is turned into a thunk and/or the rest of references are optimized out, we will not see code size decrease. In longer term I would like to get references redirected, but doing so is bit more touchy than redirecting callers. ipa-visibility already has code to bring in static variable initializers and update them. It probably should be separated and also used by ipa-icf. Redirecting references in function bodies will need new infrastructure. This is not that important issue as it may look, because in most cases we will not redirect references because we lack knowledge about ADDR_EXPR being posisbly used for pointer comparsion. For GCC 5 I guess we may want to do redirection only when symbol passes will_be_removed_from_program_if_no_direct_calls_p or when we are going to turn the function into thunk anyway. For GCC 6 we can introduce analysis to identify symbols whose address can possibly be compared for equality. Given the rising number of cases where this matter, I think doing so will be a win.
next prev parent reply other threads:[~2015-02-24 0:00 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-20 23:45 [Bug bootstrap/65150] New: bootstrap failure at r220878 " howarth at bromo dot med.uc.edu 2015-02-20 23:47 ` [Bug bootstrap/65150] " howarth at bromo dot med.uc.edu 2015-02-21 9:39 ` howarth at bromo dot med.uc.edu 2015-02-21 12:47 ` [Bug bootstrap/65150] r220875 causes bootstrap failure " dominiq at lps dot ens.fr 2015-02-21 13:47 ` iains at gcc dot gnu.org 2015-02-22 23:16 ` mrs at gcc dot gnu.org 2015-02-23 10:18 ` [Bug bootstrap/65150] [5 Regression] " rguenth at gcc dot gnu.org 2015-02-23 12:52 ` jakub at gcc dot gnu.org 2015-02-23 17:56 ` iains at gcc dot gnu.org 2015-02-23 17:58 ` dominiq at lps dot ens.fr 2015-02-23 20:47 ` howarth at bromo dot med.uc.edu 2015-02-23 22:29 ` iains at gcc dot gnu.org 2015-02-24 4:31 ` hubicka at gcc dot gnu.org [this message] 2015-02-24 14:06 ` iains at gcc dot gnu.org 2015-02-24 15:02 ` howarth at bromo dot med.uc.edu 2015-02-24 20:01 ` mrs at gcc dot gnu.org 2015-02-24 20:20 ` jakub at gcc dot gnu.org 2015-02-25 1:08 ` iains at gcc dot gnu.org 2015-02-25 3:36 ` hubicka at ucw dot cz 2015-02-25 5:18 ` hubicka at ucw dot cz 2015-02-25 22:48 ` iains at gcc dot gnu.org 2015-02-27 6:14 ` hubicka at gcc dot gnu.org 2015-02-27 7:37 ` mrs at gcc dot gnu.org 2015-02-27 8:28 ` hubicka at gcc dot gnu.org 2015-02-27 15:29 ` howarth at bromo dot med.uc.edu
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-65150-4-75OgNJ15g3@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: linkBe 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).