public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54781] [4.8 Regression] ICE in refs_may_alias_p_1, at tree-ssa-alias.c:1124 Date: Tue, 20 Nov 2012 13:50:00 -0000 [thread overview] Message-ID: <bug-54781-4-gKlk0X8qVo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54781-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54781 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-11-20 CC| |jakub at gcc dot gnu.org, | |ramana at gcc dot gnu.org Component|middle-end |target Target Milestone|--- |4.8.0 Ever Confirmed|0 |1 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-20 13:50:08 UTC --- Looks like a target bug to me, neon_dereference_pointer creates an invalid MEM_REF (the first operand on it doesn't satisfy the required is_gimple_mem_ref_addr predicate) and this invalid MEM_REF is then added by expand_normal into the MEM_EXPR of the MEM, and the aliasing code is then upset about it. In particular, the MEM_REF operand is &z[x_5(D)]. The reason why &z[x_5(D)] is in the CALL_EXPR_ARG of the builtin is expand_call_stmt optimization: /* TER addresses into arguments of builtin functions so we have a chance to infer more correct alignment information. See PR39954. */ Best would be if in this case the backend could find out the original argument, which was a SSA_NAME, and use that as the MEM_REF operand instead, but I'm afraid we don't have such a way right now. So perhaps the backend could clear MEM_EXPR if it is invalid: case NEON_ARG_MEMORY: ... if (MEM_EXPR (op[argc]) && TREE_CODE (MEM_EXPR (op[argc])) == MEM_REF && !is_gimple_mem_ref_addr (TREE_OPERAND (MEM_EXPR (op[argc]), 0))) /* Make sure MEM_EXPR created by neon_dereference_pointer isn't invalid. */ set_mem_expr (op[argc], NULL_RTX);
next prev parent reply other threads:[~2012-11-20 13:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-02 17:37 [Bug middle-end/54781] New: " Bernhard.Rosenkranzer at linaro dot org 2012-10-02 18:34 ` [Bug middle-end/54781] " Bernhard.Rosenkranzer at linaro dot org 2012-10-02 18:35 ` Bernhard.Rosenkranzer at linaro dot org 2012-11-20 13:50 ` jakub at gcc dot gnu.org [this message] 2012-12-07 11:43 ` [Bug target/54781] " rguenth at gcc dot gnu.org 2012-12-16 22:11 ` Bernhard.Rosenkranzer at linaro dot org 2012-12-17 11:26 ` jakub at gcc dot gnu.org 2012-12-17 12:39 ` rguenth at gcc dot gnu.org 2012-12-17 14:57 ` rguenth at gcc dot gnu.org 2012-12-17 15:51 ` rguenth at gcc dot gnu.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=bug-54781-4-gKlk0X8qVo@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).