public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/27561] [mingw32] floating-point extreme values are wrong Date: Tue, 30 May 2006 15:06:00 -0000 [thread overview] Message-ID: <20060530150554.8654.qmail@sourceware.org> (raw) In-Reply-To: <bug-27561-10129@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from fxcoudert at gcc dot gnu dot org 2006-05-30 15:05 ------- OK, I managed to reduce this to a GMP/MPFR bug on i386-pc-mingw32: $ cat mpfr.c #include <stdio.h> #include <gmp.h> #include <mpfr.h> int main (void) { mpfr_t b; mpfr_init (b); mpfr_set_ui (b, 2, GMP_RNDN); mpfr_out_str (stdout, 10, 0, b, GMP_RNDN); fputs ("\n", stdout); mpfr_pow_si (b, b, -23, GMP_RNDN); mpfr_out_str (stdout, 10, 0, b, GMP_RNDN); fputs ("\n", stdout); return 0; } $ gcc mpfr.c -I$HOME/local/include -L$HOME/local/lib -lmpfr -lgmp && ./a.exe 2.0000000000000000 0 while it should output (on i386-pc-linux): $ gcc mpfr.c -lmpfr -lgmp && ./a.out 2.00000000000000 1.19209289550781e-7 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27561
next prev parent reply other threads:[~2006-05-30 15:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-11 17:18 [Bug fortran/27561] New: i386-pc-mingw32 version incorrect error dir at lanl dot gov 2006-05-30 13:12 ` [Bug fortran/27561] [mingw32] floating-point extreme values are wrong fxcoudert at gcc dot gnu dot org 2006-05-30 13:17 ` fxcoudert at gcc dot gnu dot org 2006-05-30 13:59 ` fxcoudert at gcc dot gnu dot org 2006-05-30 15:06 ` fxcoudert at gcc dot gnu dot org [this message] 2006-05-30 16:34 ` dir at lanl dot gov 2006-05-30 17:01 ` dir at lanl dot gov 2006-05-31 12:54 ` fxcoudert 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=20060530150554.8654.qmail@sourceware.org \ --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).