public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/40753] [4.5 Regression] ICE in refs_may_alias_p_1 for libffi/src/powerpc/ffi.c
Date: Tue, 14 Jul 2009 21:58:00 -0000	[thread overview]
Message-ID: <20090714215824.5085.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40753-4503@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2009-07-14 21:58 -------
Huh, we end up with a FUNCTION_DECL here, from

(gdb) call debug_rtx (mem)
(mem/c/i:SI (const:SI (plus:SI (symbol_ref:SI ("ffi_closure_LINUX64") [flags
0x41] <function_decl 0xb7d4ec80 ffi_closure_LINUX64>)
            (const_int 12 [0xc]))) [0 ffi_closure_LINUX64+12 S4 A8])

that doesn't make much sense but is easy to fix.

Index: alias.c
===================================================================
--- alias.c     (revision 149643)
+++ alias.c     (working copy)
@@ -279,6 +279,11 @@ ao_ref_from_mem (ao_ref *ref, const_rtx 
       && TREE_CODE (TREE_OPERAND (base, 0)) != SSA_NAME)
     return false;

+  /* The tree oracle doesn't like to have these.  */
+  if (TREE_CODE (base) == FUNCTION_DECL
+      || TREE_CODE (base) == LABEL_DECL)
+    return false;
+
   /* If this is a reference based on a partitioned decl replace the
      base with an INDIRECT_REF of the pointer representative we
      created during stack slot partitioning.  */


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40753


  parent reply	other threads:[~2009-07-14 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 19:49 [Bug bootstrap/40753] New: " janis at gcc dot gnu dot org
2009-07-14 21:46 ` [Bug bootstrap/40753] [4.5 Regression] " rguenth at gcc dot gnu dot org
2009-07-14 21:58 ` rguenth at gcc dot gnu dot org [this message]
2009-07-15  9:26 ` rguenth at gcc dot gnu dot org
2009-07-15  9:43 ` rguenth at gcc dot gnu dot org
2009-07-23 17:52 ` hjl at gcc dot gnu dot org

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=20090714215824.5085.qmail@sourceware.org \
    --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).