From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-29402-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20880 invoked by alias); 14 Feb 2003 22:06:00 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 20862 invoked by uid 71); 14 Feb 2003 22:06:00 -0000
Resent-Date: 14 Feb 2003 22:06:00 -0000
Resent-Message-ID: <20030214220600.20860.qmail@sources.redhat.com>
Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer)
Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Resent-Reply-To: gcc-gnats@gcc.gnu.org, rwahl@gmx.de
Received: (qmail 20839 invoked by uid 48); 14 Feb 2003 22:05:58 -0000
Message-Id: <20030214220558.20838.qmail@sources.redhat.com>
Date: Fri, 14 Feb 2003 22:06:00 -0000
From: rwahl@gmx.de
Reply-To: rwahl@gmx.de
To: gcc-gnats@gcc.gnu.org
X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31)
Subject: optimization/9711: glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon, -fomit-frame-pointer)
X-SW-Source: 2003-02/txt/msg00639.txt.bz2
List-Id: <gcc-prs.sourceware.org>


>Number:         9711
>Category:       optimization
>Synopsis:       glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon, -fomit-frame-pointer)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 14 22:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Ronald Wahl
>Release:        3.2.2
>Organization:
>Environment:
Athlon TBird 1200MHz
linux-2.4.20
binutils 2.13.90.0.18 (happens with CVS head too)
>Description:
I found a bug in the code scheduler for Athlon and i686.
If compile glibc-2.3.1 (and even the current CVS head) and
optimize with "-march=i586 -mcpu=athlon" or
"-march=i586 -mcpu=i686" I get a broken
glibc or the compile fails at "sunrpc/xbootparam.T"
(segfault of a program that is started via the newly
compiled linker). This depends on the fact if I
cross-compile the glibc (between different x86 architectures or not. Broken means that some
binaries (especially those linked against libpthread)
segfault at termination. There are no problems if I compile
with "-march=i586 -mcpu=i586" or "-march=i686 -mcpu=i686".
BTW, I tried different -O levels (-O1 ... -O3). This had no
effect. Other combinations I haven't tested.

Additionally there is a problem when glibc is compiled without frame-pointers. I can reproduce this too. See here:

http://sources.redhat.com/ml/bug-glibc/2002-10/msg00072.html
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: