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 c/30858] ice for legal code with -O2 -ftree-vectorize
Date: Mon, 19 Feb 2007 12:56:00 -0000	[thread overview]
Message-ID: <20070219125604.8237.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30858-9596@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from dorit at il dot ibm dot com  2007-02-19 12:56 -------
(In reply to comment #0)

Thanks for exercising the vectorizer and reporting these bugs!

> On the wider issue of the quality of the vectorizer, I
> have thrown most of Suse Linux 10.3 at it and it has crashed
> in a few places.

only a few? :-)

> I suspect there would be considerable value at getting some
> other distribution [ Debian ?], maybe on another type of 
> machine [ PPC64 ?], and flushing out a few more bugs in the optimizer.
> You would need to ensure that -ftree-vectorize was switched
> on for every compile.
> Just a suggestion.

I agree. We are working on a cost model these days to make the vectorizer less
greedy, hopefully as a step towards enabling vectorization on by default -
which would help in flushing bugs out.

(Just as a side comment - FYI - most of the vectorizer bugs you opened so far
in the last few days (30771, 30795, 30843) are related to features that were
added *very* recently).


-- 


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


  parent reply	other threads:[~2007-02-19 12:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 11:59 [Bug c/30858] New: " dcb314 at hotmail dot com
2007-02-19 11:59 ` [Bug c/30858] " dcb314 at hotmail dot com
2007-02-19 12:45 ` dorit at il dot ibm dot com
2007-02-19 12:56 ` dorit at il dot ibm dot com [this message]
2007-02-19 13:17 ` [Bug tree-optimization/30858] [4.3 Regression] " rguenth at gcc dot gnu dot org
2007-02-19 14:12 ` dorit at il dot ibm dot com
2007-02-20 22:56 ` dorit at il dot ibm dot com
2007-02-21 12:17 ` dcb314 at hotmail dot com
2007-02-21 19:31 ` dorit at il dot ibm dot com
2007-02-22  1:01 ` patchapp at dberlin dot org
2007-02-22  8:16 ` dorit at gcc dot gnu dot org
2007-06-18  5:47 ` pinskia 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=20070219125604.8237.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).