public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/60819] dse1 removing not-dead insn (aliasing issue?)
Date: Fri, 11 Apr 2014 12:23:00 -0000	[thread overview]
Message-ID: <bug-60819-4-o5jbW5KLV1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60819-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, eventually better representation:

Index: gcc/c-family/c-common.c
===================================================================
--- gcc/c-family/c-common.c     (revision 209298)
+++ gcc/c-family/c-common.c     (working copy)
@@ -11760,20 +11760,18 @@ convert_vector_to_pointer_for_subscript
 {
   if (TREE_CODE (TREE_TYPE (*vecp)) == VECTOR_TYPE)
     {
-      tree type = TREE_TYPE (*vecp);
-      tree type1;
+      tree vtype = TREE_TYPE (*vecp);
+      tree type;

       if (TREE_CODE (index) == INTEGER_CST)
         if (!tree_fits_uhwi_p (index)
-            || tree_to_uhwi (index) >= TYPE_VECTOR_SUBPARTS (type))
+            || tree_to_uhwi (index) >= TYPE_VECTOR_SUBPARTS (vtype))
           warning_at (loc, OPT_Warray_bounds, "index value is out of bound");

       c_common_mark_addressable_vec (*vecp);
-      type = build_qualified_type (TREE_TYPE (type), TYPE_QUALS (type));
-      type = build_pointer_type (type);
-      type1 = build_pointer_type (TREE_TYPE (*vecp));
-      *vecp = build1 (ADDR_EXPR, type1, *vecp);
-      *vecp = convert (type, *vecp);
+      type = build_qualified_type (TREE_TYPE (vtype), TYPE_QUALS (vtype));
+      type = build_array_type_nelts (type, TYPE_VECTOR_SUBPARTS (vtype));
+      *vecp = build1 (VIEW_CONVERT_EXPR, type, *vecp);
     }
 }

which defers the "issue" to RTL expansion, expanding from

  _3 = VIEW_CONVERT_EXPR<short int[4]>(__A_5(D))[__N_2(D)];
  _4 = (int) _3;
  return _4;


  parent reply	other threads:[~2014-04-11 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11 11:37 [Bug rtl-optimization/60819] New: " glisse at gcc dot gnu.org
2014-04-11 12:09 ` [Bug c/60819] " rguenth at gcc dot gnu.org
2014-04-11 12:23 ` rguenth at gcc dot gnu.org [this message]
2014-04-11 12:25 ` rguenth at gcc dot gnu.org
2014-04-11 12:26 ` rguenth at gcc dot gnu.org
2014-04-11 12:27 ` glisse at gcc dot gnu.org
2014-04-11 12:31 ` rguenther at suse dot de
2014-04-11 12:32 ` rguenth at gcc dot gnu.org
2014-04-11 12:43 ` glisse at gcc dot gnu.org
2014-04-11 12:51 ` rguenther at suse dot de
2014-04-11 13:16 ` glisse at gcc dot gnu.org
2014-04-11 13:19 ` glisse at gcc dot gnu.org
2014-04-12  8:30 ` glisse at gcc dot gnu.org
2014-04-14 11:59 ` rguenth at gcc dot gnu.org
2014-04-22 13:26 ` rguenth at gcc dot gnu.org
2014-05-23  9:50 ` 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-60819-4-o5jbW5KLV1@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).