public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: aganse@apl.washington.edu
To: gcc-gnats@gcc.gnu.org
Subject: fortran/8587: (double complex zero)**(double prec number) = NAN instead of zero
Date: Thu, 21 Nov 2002 05:22:00 -0000	[thread overview]
Message-ID: <20021115014122.16426.qmail@sources.redhat.com> (raw)


>Number:         8587
>Category:       fortran
>Synopsis:       (double complex zero)**(double prec number) = NAN instead of zero
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 14 17:46:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Andy Ganse, Applied Physics Laboratory, Seattle
>Release:        GNU Fortran 0.5.26 20000731 (Red Hat Linux 7.2 2.96-112.7.2) and also GNU Fortran 0.5.25 19991024
>Organization:
>Environment:
GNU Fortran 0.5.26 20000731 on RedHat i386/7.3 on athlon
GNU Fortran 0.5.25 19991024 on SunOS 5.8 on Sun-Blade-1000
>Description:
There are a couple situations (produced in the small attached test source file) when a double complex variable set to zero, and raised to the power of another variable, is not equaling zero - it's coming out as NAN instead.  This all works fine in Sun F77 if that's useful for comparison...
The case where a double complex variable equaling zero is raised to a real (as opposed to double precision) constant works here but is producing slightly off values in our program when the double complex variable does not equal zero.
>How-To-Repeat:
compile and run the attached dprec.f
>Fix:
?
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="dprec.f"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="dprec.f"

CiAgICAgIGRvdWJsZSBjb21wbGV4IGRjMSwgZGMyLCBkYzMsIGRjNCwgZGM1LCBkYzYKICAgICAg
ZG91YmxlIHByZWNpc2lvbiBkMSwgZDIKICAgICAgcmVhbCByMQogICAgICBkYzE9ZGNtcGx4KDAu
ZDAsMC5kMCkKICAgICAgZDE9MgogICAgICBkMj0yLmQwCiAgICAgIHIxPTIKICAgICAgZGMyPWRj
MSoqZDEKICAgICAgZGMzPWRjMSoqZDIKICAgICAgZGM0PWRjMSoqcjEKICAgICAgZGM1PWRjMSoq
MgogICAgICBkYzY9ZGMxKioyLmQwCiAgICAgIHByaW50ICosIGRjMSwgZGMyLCBkYzMsIGRjNCwg
ZGM1LCBkYzYKCmMgICAgIGlzIHByb2R1Y2luZzoKYyAgICAgKDAuLDAuKSAoTkFOLE5BTikgKE5B
TixOQU4pIChOQU4sTkFOKSAoMC4sMC4pIChOQU4sTkFOKQpjICAgICBpbnN0ZWFkIG9mOgpjICAg
ICAoMC4sMC4pICgwLiwwLikgKDAuLDAuKSAoMC4sMC4pICgwLiwwLikgKDAuLDAuKQoKICAgICAg
ZW5kIAo=


             reply	other threads:[~2002-11-15  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21  5:22 aganse [this message]
2002-11-24 10:58 toon
2002-11-27  7:31 toon

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=20021115014122.16426.qmail@sources.redhat.com \
    --to=aganse@apl.washington.edu \
    --cc=gcc-gnats@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).