From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24297 invoked by alias); 12 Mar 2008 11:06:02 -0000 Received: (qmail 24182 invoked by uid 48); 12 Mar 2008 11:05:19 -0000 Date: Wed, 12 Mar 2008 11:06:00 -0000 Message-ID: <20080312110519.24181.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/30442] Expanded array initialization can use memset builtin function In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ubizjak at gmail 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: 2008-03/txt/msg00877.txt.bz2 ------- Comment #4 from ubizjak at gmail dot com 2008-03-12 11:05 ------- This still happens on mainline. I wonder if vectorizer infrastructure can be re-used here to detect unrolled and looped version of memset. In addition to loop that can be "vectorized", we have something resembling "vectorization" of straight code. And looking at comment #3, the rewards from real-world code look really promising. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30442