public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dorit at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/24963] [4.1/4.2 Regression] gcc.dg/vect/vect-62.c scan-tree-dump-times not vectorized: redundant loop. no profit to vectorize. 1 fails
Date: Mon, 05 Dec 2005 14:17:00 -0000	[thread overview]
Message-ID: <20051205141756.14936.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24963-230@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from dorit at il dot ibm dot com  2005-12-05 14:17 -------
> Dorit, is it only a matter of changing the expected error message?

Yes - the error message checks that the vectorizer detected that it's not worth
while to vectorize the loop because all operations in the loop are either dead
or only used outside the loop and can be moved out of the loop (e.g.
invariants, inductions). In other words - the loop should have been optimized
away by scalar optimizations. Indeed, this is what now happens - so the
specific loop that issued this message does not exist anymore. This dg line can
be removed from the test.


-- 


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


  parent reply	other threads:[~2005-12-05 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20 17:59 [Bug tree-optimization/24963] New: " jsm28 at gcc dot gnu dot org
2005-11-21  0:53 ` [Bug tree-optimization/24963] " pinskia at gcc dot gnu dot org
2005-12-05  7:59 ` ebotcazou at gcc dot gnu dot org
2005-12-05 14:17 ` dorit at il dot ibm dot com [this message]
2005-12-05 18:53 ` ebotcazou at gcc dot gnu dot org
2005-12-05 18:54 ` ebotcazou at gcc dot gnu dot org
2005-12-05 18:56 ` ebotcazou 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=20051205141756.14936.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).