From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27771 invoked by alias); 7 Oct 2002 11:16:06 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 27755 invoked by uid 71); 7 Oct 2002 11:16:05 -0000 Date: Mon, 07 Oct 2002 04:16:00 -0000 Message-ID: <20021007111605.27754.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Andreas Steinmetz Subject: Re: optimization/8156: -mcpu=pentium4 generates wrong fp results in glibc-2.3 Reply-To: Andreas Steinmetz X-SW-Source: 2002-10/txt/msg00249.txt.bz2 List-Id: The following reply was made to PR optimization/8156; it has been noted by GNATS. From: Andreas Steinmetz 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.