public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/35045] New: gcc-4.3 generates wrong code on i386 with -O3
Date: Thu, 31 Jan 2008 22:57:00 -0000 [thread overview]
Message-ID: <bug-35045-8932@http.gcc.gnu.org/bugzilla/> (raw)
The attached code, coming from the GNU libc (test-ifloat.c and
s_cacoshf.c) gives wrong results when compiled with gcc-4.3 and -O3. The
results are correct with gcc-4.3 and lower optimizations, or with gcc-4.2.
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3-20080127-1'
--with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
--enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.3.0 20080127 (experimental) [trunk revision 131882] (Debian
4.3-20080127-1)
--
Summary: gcc-4.3 generates wrong code on i386 with -O3
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: aurelien at aurel32 dot net
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35045
next reply other threads:[~2008-01-31 22:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 22:57 aurelien at aurel32 dot net [this message]
2008-01-31 22:59 ` [Bug c/35045] " aurelien at aurel32 dot net
2008-01-31 23:00 ` [Bug middle-end/35045] " pinskia at gcc dot gnu dot org
2008-01-31 23:11 ` [Bug c/35045] " aurelien at aurel32 dot net
2008-01-31 23:17 ` aurelien at aurel32 dot net
2008-02-01 10:34 ` [Bug target/35045] [4.3 Regression] " rguenth at gcc dot gnu dot org
2008-02-01 10:46 ` ismail at pardus dot org dot tr
2008-02-01 10:55 ` rguenth at gcc dot gnu dot org
2008-02-01 11:51 ` stevenb dot gcc at gmail dot com
2008-02-01 11:54 ` steven at gcc dot gnu dot org
2008-02-01 11:59 ` rguenth at gcc dot gnu dot org
2008-02-01 12:03 ` rguenth at gcc dot gnu dot org
2008-02-01 12:54 ` rguenth at gcc dot gnu dot org
2008-02-01 13:04 ` rguenth at gcc dot gnu dot org
2008-02-01 13:16 ` rguenth at gcc dot gnu dot org
2008-02-01 13:19 ` steven at gcc dot gnu dot org
2008-02-01 14:09 ` rguenth at gcc dot gnu dot org
2008-02-01 14:14 ` rguenth at gcc dot gnu dot org
2008-02-01 14:14 ` stevenb dot gcc at gmail dot com
2008-02-01 14:39 ` rguenther at suse dot de
2008-02-01 14:41 ` matz at gcc dot gnu dot org
2008-02-01 14:46 ` matz at gcc dot gnu dot org
2008-02-01 14:56 ` stevenb dot gcc at gmail dot com
2008-02-01 15:00 ` matz at gcc dot gnu dot org
2008-02-01 15:10 ` steven at gcc dot gnu dot org
2008-02-01 18:54 ` debian-gcc at lists dot debian dot org
2008-02-02 15:02 ` matz at gcc dot gnu dot org
2008-02-02 15:06 ` matz at gcc dot gnu dot org
2008-02-03 8:42 ` dominiq at lps dot ens dot fr
2008-02-03 11:29 ` ubizjak at gmail dot com
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=bug-35045-8932@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).