public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "irar at il dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49628] [4.7 Regression] 447.dealII in SPEC CPU 2006 failed to build
Date: Tue, 05 Jul 2011 08:18:00 -0000	[thread overview]
Message-ID: <bug-49628-4-xxBeHec1vX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49628-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Ira Rosen <irar at il dot ibm.com> 2011-07-05 08:18:09 UTC ---
Sorry, I was wrong about group size check. It is ok without your patch. So,
this should be enough:

Index: tree-vect-data-refs.c
===================================================================
--- tree-vect-data-refs.c       (revision 175785)
+++ tree-vect-data-refs.c       (working copy)
@@ -2304,7 +2304,10 @@ vect_analyze_data_ref_access (struct dat

   /* Allow invariant loads in loops.  */
   if (loop_vinfo && dr_step == 0)
-    return DR_IS_READ (dr);
+    {
+      GROUP_FIRST_ELEMENT (vinfo_for_stmt (stmt)) = NULL;
+      return DR_IS_READ (dr);
+    }

   if (loop && nested_in_vect_loop_p (loop, stmt))
     {

Thanks,
Ira


  parent reply	other threads:[~2011-07-05  8:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 13:27 [Bug middle-end/49628] New: " hjl.tools at gmail dot com
2011-07-04 13:39 ` [Bug middle-end/49628] " rguenth at gcc dot gnu.org
2011-07-04 14:02 ` hjl.tools at gmail dot com
2011-07-04 14:26 ` rguenth at gcc dot gnu.org
2011-07-04 14:33 ` rguenth at gcc dot gnu.org
2011-07-04 15:07 ` rguenth at gcc dot gnu.org
2011-07-05  6:44 ` irar at il dot ibm.com
2011-07-05  8:18 ` irar at il dot ibm.com [this message]
2011-07-05  8:54 ` rguenth at gcc dot gnu.org
2011-07-05 11:25 ` rguenth at gcc dot gnu.org
2011-07-05 11:27 ` rguenth at gcc dot gnu.org
2011-07-06  8:11 ` rguenth at gcc dot gnu.org
2011-09-08 10:49 ` 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-49628-4-xxBeHec1vX@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).