public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zimmerma+gcc at loria dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/40757] New: gcc 4.4.0 miscompiles mpfr-2.4.1 Date: Wed, 15 Jul 2009 00:36:00 -0000 [thread overview] Message-ID: <bug-40757-16207@http.gcc.gnu.org/bugzilla/> (raw) See http://websympa.loria.fr/wwsympa/arc/mpfr/2009-07/msg00031.html and the following discussion. This was on t2.math.washington.edu with /usr/local/gcc-4.4.0-sun-linker/bin/gcc: zimmerma@t2:/tmp/mpfr-2.4.1$ /usr/local/gcc-4.4.0-sun-linker/bin/gcc -v Using built-in specs. Target: sparc-sun-solaris2.10 Configured with: /home/kirkby/gcc-4.4.0/configure CC=/usr/sfw/bin/gcc --prefix=/usr/local/gcc-4.4.0-sun-linker --without-gnu-as --without-gnu-ld --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable-languages=c,c++,fortran --with-mpfr-lib=/usr/local/lib --with-mpfr-include=/usr/local/include --with-gmp-include=/usr/local/include --with-gmp-lib=/usr/local/lib --with-libiconv-prefix=/usr/lib/iconv Thread model: posix gcc version 4.4.0 (GCC) -- Summary: gcc 4.4.0 miscompiles mpfr-2.4.1 Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: zimmerma+gcc at loria dot fr GCC build triplet: sparc-sun-solaris2.10 GCC host triplet: sparc-sun-solaris2.10 GCC target triplet: sparc-sun-solaris2.10 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40757
next reply other threads:[~2009-07-15 0:36 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-15 0:36 zimmerma+gcc at loria dot fr [this message] 2009-07-15 2:02 ` [Bug c/40757] " zimmerma+gcc at loria dot fr 2009-07-15 6:27 ` ebotcazou at gcc dot gnu dot org 2009-07-15 9:55 ` rguenth at gcc dot gnu dot org 2009-07-15 13:15 ` mikpe at it dot uu dot se 2009-07-16 7:52 ` zimmerma+gcc at loria dot fr 2009-07-16 8:31 ` mikpe at it dot uu dot se 2009-07-16 10:19 ` david dot kirkby at onetel dot net 2009-07-16 10:24 ` david dot kirkby at onetel dot net 2009-07-16 10:31 ` jakub at gcc dot gnu dot org 2009-07-16 12:32 ` david dot kirkby at onetel dot net 2009-07-16 14:07 ` jakub at gcc dot gnu dot org 2009-07-16 20:34 ` marc dot glisse at normalesup dot org 2009-07-16 21:29 ` david dot kirkby at onetel dot net 2009-07-17 0:58 ` zimmerma+gcc at loria dot fr 2009-07-17 3:22 ` david dot kirkby at onetel dot net 2009-07-17 4:11 ` david dot kirkby at onetel dot net 2009-07-17 7:49 ` jakub at gcc dot gnu dot org 2009-07-17 11:19 ` david dot kirkby at onetel dot net 2009-07-17 15:51 ` marc dot glisse at normalesup dot org 2009-07-18 1:14 ` david dot kirkby at onetel dot net 2009-07-18 1:18 ` david dot kirkby at onetel dot net 2009-07-18 4:50 ` marc dot glisse at normalesup dot org 2009-07-18 14:36 ` david dot kirkby at onetel dot net 2009-07-18 14:44 ` david dot kirkby at onetel dot net 2009-07-18 19:33 ` david dot kirkby at onetel dot net 2009-10-01 8:34 ` [Bug target/40757] " david dot kirkby at onetel dot net 2009-10-04 11:01 ` ebotcazou at gcc dot gnu dot org
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-40757-16207@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: linkBe 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).