public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/47056] [4.6 Regression] 10 Ada ACATS tests fail to link with undefined reference on ia64-linux
Date: Sun, 02 Jan 2011 19:14:00 -0000 [thread overview]
Message-ID: <bug-47056-4-6vEm8pI67H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47056-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47056
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-01-02 19:14:22 UTC ---
The problem is that CCP turns:
pr47056___alignment.46_308 = pr47056___alignment;
D.2264_309 = MEM[(struct *)pr47056___alignment.46_308].D.227;
into
D.2264_309 = MEM[(struct *)pr47056___alignment].D.227;
(pr47056___alignment being a function) and while walk_stmt_load_store_addr_ops
recognizes the former as an address-of pattern (the & is implicit for
functions), it doesn't for the latter (unlike for TARGET_MEM_REF) so
build_cgraph_edges is fooled and missed the reference to pr47056___alignment.
Richard, I presume that the latter form must be deemed invalid GIMPLE?
next prev parent reply other threads:[~2011-01-02 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 20:21 [Bug ada/47056] New: " laurent at guerby dot net
2010-12-27 19:05 ` [Bug ada/47056] " jakub at gcc dot gnu.org
2010-12-27 22:26 ` laurent at guerby dot net
2010-12-28 8:48 ` laurent at guerby dot net
2010-12-28 15:22 ` ebotcazou at gcc dot gnu.org
2010-12-28 15:23 ` ebotcazou at gcc dot gnu.org
2011-01-02 19:14 ` ebotcazou at gcc dot gnu.org [this message]
2011-01-04 10:51 ` [Bug tree-optimization/47056] " ebotcazou at gcc dot gnu.org
2011-01-04 10:53 ` ebotcazou at gcc dot gnu.org
2011-01-04 23:22 ` ebotcazou at gcc dot gnu.org
2011-01-04 23:26 ` ebotcazou at gcc dot gnu.org
2011-01-10 11:47 ` laurent at guerby dot net
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-47056-4-6vEm8pI67H@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).