public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/17927] Math error in simple divide operation
Date: Tue, 12 Oct 2004 04:57:00 -0000 [thread overview]
Message-ID: <20041012045739.14814.qmail@sourceware.org> (raw)
In-Reply-To: <20041011051839.17927.jvdelisle@verizon.net>
------- Additional Comments From jvdelisle at verizon dot net 2004-10-12 04:57 -------
Subject: Re: Math error in simple divide operation
On Mon, 2004-10-11 at 09:00, tobi at gcc dot gnu dot org wrote:
> ------- Additional Comments From tobi at gcc dot gnu dot org 2004-10-11 16:00 -------
> Actually, looking at this again, gfortran's behavior is correct.
>
> If you had written
> big = 2.0_8 / 3.0_8
> you would have gotten the result you were expecting.
>
> I think, adding a warning would be the best route for "fixing" this problem.
I tried this same program with g95 before I submitted a bug and got what
I thought was the correct results without needing the additional _8 .
Do the standards specify that default precision for constants is kind=4?
I suppose then that a warning would be good when mixing precisions in
assignments.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17927
next prev parent reply other threads:[~2004-10-12 4:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 5:18 [Bug fortran/17927] New: " jvdelisle at verizon dot net
2004-10-11 5:28 ` [Bug fortran/17927] " pinskia at gcc dot gnu dot org
2004-10-11 15:54 ` tobi at gcc dot gnu dot org
2004-10-11 16:00 ` tobi at gcc dot gnu dot org
2004-10-12 4:57 ` jvdelisle at verizon dot net [this message]
2004-10-12 6:55 ` anlauf at hep dot tu-darmstadt dot de
2004-10-12 21:26 ` tobi at gcc dot gnu dot org
2004-10-21 15:25 ` tobi at gcc dot gnu dot org
2005-01-06 14:27 ` 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=20041012045739.14814.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: 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).