From mboxrd@z Thu Jan  1 00:00:00 1970
From: rwhaley@cs.utk.edu
To: gcc-gnats@gcc.gnu.org
Cc: rwhaley@cs.utk.edu
Subject: c/3913: On Athlon's, gcc 3.0 produces code running 1/2 as fast as gcc 2.95
Date: Wed, 01 Aug 2001 17:56:00 -0000
Message-id: <20010802005022.26072.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-08/msg00035.html
List-Id: <gcc-prs.sourceware.org>

>Number:         3913
>Category:       c
>Synopsis:       On Athlon's, gcc 3.0 produces code running 1/2 as fast as gcc 2.95
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          pessimizes-code
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 01 17:56:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     rwhaley@cs.utk.edu
>Release:        gcc version 3.0
>Organization:
>Environment:
RedHat Linux 7.1 on a 1.2Ghz Athlon.  gcc -v gives:
hades. /usr/local/gcc-3.0/bin/gcc -v
Reading specs from /usr/local/gcc-3.0/lib/gcc-lib/i686-pc-linux-gnu/3.0/specs
Configured with: ./configure --prefix=/usr/local/gcc-3.0
Thread model: single
gcc version 3.0
>Description:
The new memory fetch scheduling algorithm reduces Athlon performance by a factor of 2 over the one used by gcc 2.95.x.  It also appears that the x87 register stack utilization algorithm  is worse than 2.95.x as well. 

Problem is too complex to reduce to 1 single preprocessed file.  The full problem is detailed (along with code to reproduce, and assembler outputs) here: 
   http://www.cs.utk.edu/~rwhaley/ATLAS/gcc30.html
    
   
>How-To-Repeat:
 http://www.cs.utk.edu/~rwhaley/ATLAS/gcc30.html#dup
>Fix:
Have option to use 2.95 scheduler for scheduling problem.
Have option to use 2.95 x87 register stack for register stack usage problem.
>Release-Note:
>Audit-Trail:
>Unformatted: