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 tree-optimization/49006] [4.6/4.7 Regression] Missed vectorization due to revision 167531
Date: Tue, 02 Aug 2011 09:21:00 -0000	[thread overview]
Message-ID: <bug-49006-4-JeG2oYbrnT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49006-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Ira Rosen <irar at il dot ibm.com> 2011-08-02 09:21:26 UTC ---
Basic block SLP only prints "basic block vectorized using SLP". But I thought
we are talking about loop vectorization here, since the early unrolling is
applied only if there is an outer loop as well (correct?), so it should be the
same "LOOP VECTORIZED". And I see with on trunk:

induct.f90:1757: note: LOOP VECTORIZED.
induct.f90:2168: note: LOOP VECTORIZED.

and 1757 is the outer loop of 1766, and 2168 is the outer loop of 2177.

These loops are not vectorized with 4.6 though.

Ira


  parent reply	other threads:[~2011-08-02  9:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 18:45 [Bug tree-optimization/49006] New: " dominiq at lps dot ens.fr
2011-05-16  9:30 ` [Bug tree-optimization/49006] " rguenther at suse dot de
2011-05-16 10:29 ` dominiq at lps dot ens.fr
2011-05-16 10:50 ` rguenther at suse dot de
2011-05-16 11:39 ` rguenth at gcc dot gnu.org
2011-05-19 12:53 ` irar at il dot ibm.com
2011-05-22 12:46 ` dominiq at lps dot ens.fr
2011-06-27 15:36 ` jakub at gcc dot gnu.org
2011-08-01 14:45 ` rguenth at gcc dot gnu.org
2011-08-01 14:50 ` irar at il dot ibm.com
2011-08-02  8:38 ` rguenther at suse dot de
2011-08-02  9:21 ` irar at il dot ibm.com [this message]
2011-08-02  9:25 ` rguenther at suse dot de
2011-09-16 16:19 ` dominiq at lps dot ens.fr

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-49006-4-JeG2oYbrnT@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).