From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8309 invoked by alias); 19 Feb 2007 12:56:19 -0000 Received: (qmail 8240 invoked by uid 48); 19 Feb 2007 12:56:04 -0000 Date: Mon, 19 Feb 2007 12:56:00 -0000 Message-ID: <20070219125604.8237.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/30858] ice for legal code with -O2 -ftree-vectorize In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dorit at il dot ibm dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-02/txt/msg02192.txt.bz2 ------- 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