public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65064] [5 regression] FAIL: gcc.dg/torture/pr60115.c -O1 (test for excess errors) Date: Wed, 18 Feb 2015 17:24:00 -0000 [thread overview] Message-ID: <bug-65064-4-0uoIHtVzg3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65064 --- Comment #17 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> --- Author: hjl Date: Wed Feb 18 17:24:20 2015 New Revision: 220792 URL: https://gcc.gnu.org/viewcvs?rev=220792&root=gcc&view=rev Log: Return false for common symbols in sdata_symbolic_operand Although common symbols are defined in executables, they aren't in small data section. But a definition in small data section overrides a common symbol, which still binds lcoally, and turns a reference to common symbol to reference to small data section. Even if ia64_in_small_data_p returns true on common symbols, sdata_symbolic_operand must return false on common symbols. Common symbols are assumed to be placed in small data section, but are accessed as if they are in normal data section so that they won't cause any relocation overflow. PR target/65064 * config/ia64/predicates.md (sdata_symbolic_operand): Return false for common symbols. Modified: trunk/gcc/ChangeLog trunk/gcc/config/ia64/predicates.md
next prev parent reply other threads:[~2015-02-18 17:24 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-14 20:39 [Bug rtl-optimization/65064] New: [5.0 " schwab@linux-m68k.org 2015-02-15 1:50 ` [Bug rtl-optimization/65064] " hjl.tools at gmail dot com 2015-02-15 2:03 ` hjl.tools at gmail dot com 2015-02-15 2:14 ` hjl.tools at gmail dot com 2015-02-15 13:01 ` [Bug target/65064] " schwab@linux-m68k.org 2015-02-15 13:15 ` hjl.tools at gmail dot com 2015-02-15 14:07 ` schwab@linux-m68k.org 2015-02-15 14:20 ` hjl.tools at gmail dot com 2015-02-16 9:34 ` schwab@linux-m68k.org 2015-02-16 10:15 ` [Bug target/65064] [5 " rguenth at gcc dot gnu.org 2015-02-16 10:52 ` schwab@linux-m68k.org 2015-02-16 12:42 ` schwab@linux-m68k.org 2015-02-16 12:53 ` hjl.tools at gmail dot com 2015-02-17 9:02 ` schwab@linux-m68k.org 2015-02-17 11:35 ` schwab@linux-m68k.org 2015-02-18 12:02 ` schwab@linux-m68k.org 2015-02-18 13:20 ` hjl.tools at gmail dot com 2015-02-18 17:24 ` hjl at gcc dot gnu.org [this message] 2015-02-18 17:25 ` hjl.tools 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-65064-4-0uoIHtVzg3@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).