public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rwahl@gmx.de
To: gcc-gnats@gcc.gnu.org
Subject: optimization/9711: glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon, -fomit-frame-pointer)
Date: Fri, 14 Feb 2003 22:06:00 -0000 [thread overview]
Message-ID: <20030214220558.20838.qmail@sources.redhat.com> (raw)
>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:
next reply other threads:[~2003-02-14 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 22:06 rwahl [this message]
2003-02-14 22:15 bangerth
2003-02-15 21:46 Ronald Wahl
2003-02-17 17:16 Wolfgang Bangerth
2003-02-17 18:36 Ronald Wahl
2003-02-17 22:06 Wolfgang Bangerth
2003-05-14 23:06 Dara Hazeghi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030214220558.20838.qmail@sources.redhat.com \
--to=rwahl@gmx.de \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).