From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29284 invoked by alias); 10 May 2005 09:03:58 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 27349 invoked by uid 48); 10 May 2005 09:03:43 -0000 Date: Tue, 10 May 2005 09:03:00 -0000 From: "jbucata at tulsaconnect dot com" To: gcc-bugs@gcc.gnu.org Message-ID: <20050510090336.21485.jbucata@tulsaconnect.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug rtl-optimization/21485] New: BYTEmark numsort: performance regression 3.4.3 -> 4.0.0 with -O3 optimization X-Bugzilla-Reason: CC X-SW-Source: 2005-05/txt/msg01308.txt.bz2 List-Id: I've found a major performance regression in gcc 4.0.0's optimization of the BYTEmark numsort benchmark. I've boiled it down to a testcase that I think will suit you... it outputs a single number representing the number of iterations run (higher is better). On my machine I get 900ish under 4.0.0 and around 1530 on 3.4.3. Both were compiled and run in a Gentoo test partition, if that makes a difference: 3.4.3: gcc version 3.4.3-20050110 (Gentoo Linux 3.4.3.20050110-r2, ssp-3.4.3.20050110-0, pie-8.7.7) 4.0.0: gcc version 4.0.0 (Gentoo Linux 4.0.0) -- Summary: BYTEmark numsort: performance regression 3.4.3 -> 4.0.0 with -O3 optimization Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jbucata at tulsaconnect dot com CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21485