public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/15205] [gfortran] NEAREST intrinsic returns wrong value in DOUBLE PRECISION Date: Thu, 29 Apr 2004 18:57:00 -0000 [thread overview] Message-ID: <20040429182525.31068.qmail@sources.redhat.com> (raw) In-Reply-To: <20040429173856.15205.kargl@c-67-168-59-70.client.comcast.net> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-04-29 18:25 ------- I can confirm this on i686-pc-linux-gnu but works on power-apple-darwin for some reason. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|fortran |libfortran Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2004-04-29 18:25:25 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15205
next prev parent reply other threads:[~2004-04-29 18:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-29 18:01 [Bug fortran/15205] New: " gcc-bugzilla at gcc dot gnu dot org 2004-04-29 18:13 ` [Bug fortran/15205] [gfortran] " pinskia at gcc dot gnu dot org 2004-04-29 18:57 ` pinskia at gcc dot gnu dot org [this message] 2004-04-30 0:51 ` [Bug libfortran/15205] " bdavis9659 at comcast dot net 2004-04-30 16:44 ` [Bug fortran/15205] " Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-04-30 17:06 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-04-30 18:13 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-05-01 3:01 ` bdavis at gcc dot gnu dot org 2004-05-08 16:17 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-05-08 17:28 ` pinskia at gcc dot gnu dot org 2004-05-14 18:38 ` cvs-commit at gcc dot gnu dot org 2004-05-14 18:52 ` tobi 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=20040429182525.31068.qmail@sources.redhat.com \ --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).