public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8156: -mcpu=pentium4 generates wrong fp results in glibc-2.3
Date: Mon, 07 Oct 2002 04:16:00 -0000	[thread overview]
Message-ID: <20021007111605.27754.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/8156; it has been noted by GNATS.

From: Andreas Steinmetz <ast@domdv.de>
To: gcc-gnats@gcc.gnu.org,  gcc-prs@gcc.gnu.org,  bregor@sf.anu.edu.au, 
 gcc-bugs@gcc.gnu.org,  nobody@gcc.gnu.org
Cc:  
Subject: Re: optimization/8156: -mcpu=pentium4 generates wrong fp results
 in glibc-2.3
Date: Mon, 07 Oct 2002 13:13:19 +0200

  > This is a glibc bug, not a gcc bug.
 
 I'm not so sure that it is a problem of glibc only. In my case building 
 glibc 2.3 with gcc 3.2 (release)/binutils 2.13 (release) succeeds in all 
 cases but:
 
 1. CFLAGS="-O3 -mcpu=pentiumpro -march=pentiumpro" produces a working
     glibc
 
 2. CFLAGS="-O3 -fomit-frame-pointer -mcpu=pentiumpro -march=pentiumpro"
     produces a glibc with defunct pthreads (hangs and segfaults of
     threaded processes), strace-ing these processes indicate defunct
     signal handling
 
 As it seems that "-fomit-frame-pointer" does trigger the problems it 
 could well be that there is a gcc bug.
 


             reply	other threads:[~2002-10-07 11:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07  4:16 Andreas Steinmetz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 10:27 giovannibajo
2003-05-13 18:46 Dara Hazeghi
2002-10-07  4:56 Richard Henderson
2002-10-06 21:46 Andreas Jaeger
2002-10-06 20:06 bregor

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=20021007111605.27754.qmail@sources.redhat.com \
    --to=ast@domdv.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).