public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/67417] powerpc64 bootstrap with -mcmodel=small results in linker error Date: Tue, 01 Sep 2015 23:05:00 -0000 [thread overview] Message-ID: <bug-67417-4-Q0Z3tNUEAk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67417-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67417 --- Comment #5 from Alan Modra <amodra at gcc dot gnu.org> --- Author: amodra Date: Tue Sep 1 23:04:58 2015 New Revision: 227387 URL: https://gcc.gnu.org/viewcvs?rev=227387&root=gcc&view=rev Log: [RS6000] Weak functions may not be file local A weak symbol defined in the current object file may not turn out to be the definition used at link time, if other copies of the symbol exist. This means they can't be considered file local. PR target/67417 * config/rs6000/predicates.md (current_file_function_operand): Don't return true for weak symbols. * config/rs6000/rs6000.c (rs6000_function_ok_for_sibcall): Likewise. Modified: branches/gcc-5-branch/gcc/ChangeLog branches/gcc-5-branch/gcc/config/rs6000/predicates.md branches/gcc-5-branch/gcc/config/rs6000/rs6000.c
next prev parent reply other threads:[~2015-09-01 23:05 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-01 4:52 [Bug target/67417] New: " amodra at gmail dot com 2015-09-01 4:53 ` [Bug target/67417] " amodra at gmail dot com 2015-09-01 5:44 ` amodra at gmail dot com 2015-09-01 13:17 ` amodra at gmail dot com 2015-09-01 23:03 ` amodra at gcc dot gnu.org 2015-09-01 23:05 ` amodra at gcc dot gnu.org [this message] 2015-09-01 23:26 ` amodra at gcc dot gnu.org 2015-09-01 23:28 ` amodra at gmail dot com
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-67417-4-Q0Z3tNUEAk@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).