public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dpozar at ecs dot umass.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/98201] CSQRT function gives bad resuts at runtime
Date: Tue, 08 Dec 2020 20:46:56 +0000 [thread overview]
Message-ID: <bug-98201-4-xwChfpX5aI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98201-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98201
--- Comment #11 from dpozar at ecs dot umass.edu ---
Thomas,
that looks good. But I am not sure how to proceed ...
dave
________________________________
From: tkoenig at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
Sent: Tuesday, December 8, 2020 2:27 PM
To: David Pozar <dpozar@ecs.umass.edu>
Subject: [Bug fortran/98201] CSQRT function gives bad resuts at runtime
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98201
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I don't have a working mingw system myself, but I dusted off my cygwin
system for this, using their cross-compiler to mingw.
With
$ x86_64-w64-mingw32-gfortran.exe -static -static-libgfortran csqrt.f90
this gave
Argument SquareRoot SR squared
(-.1000E+02 0.1000E+00) (0.1581E-01 0.3162E+01) (-.1000E+02 0.1000E+00)
(-.1000E+03 0.1000E+00) (0.5000E-02 0.1000E+02) (-.1000E+03 0.1000E+00)
(-.1000E+04 0.1000E+00) (0.1581E-02 0.3162E+02) (-.1000E+04 0.1000E+00)
(-.1000E+05 0.1000E+00) (0.5000E-03 0.1000E+03) (-.1000E+05 0.1000E+00)
(-.1000E+06 0.1000E+00) (0.1581E-03 0.3162E+03) (-.1000E+06 0.1000E+00)
(-.1000E+07 0.1000E+00) (0.5000E-04 0.1000E+04) (-.1000E+07 0.1000E+00)
(-.1000E+08 0.1000E+00) (0.1581E-04 0.3162E+04) (-.1000E+08 0.1000E+00)
(-.1000E+09 0.1000E+00) (0.5000E-05 0.1000E+05) (-.1000E+09 0.1000E+00)
(-.1000E+10 0.1000E+00) (0.1581E-05 0.3162E+05) (-.1000E+10 0.1000E+00)
which is OK (I tried the program both from the cygwin command line and
the cmd prompt).
--
You are receiving this mail because:
You reported the bug.
next prev parent reply other threads:[~2020-12-08 20:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 14:44 [Bug fortran/98201] New: " pozar at ecs dot umass.edu
2020-12-08 15:34 ` [Bug fortran/98201] " tkoenig at gcc dot gnu.org
2020-12-08 15:35 ` dominiq at lps dot ens.fr
2020-12-08 15:47 ` dpozar at ecs dot umass.edu
2020-12-08 15:54 ` dpozar at ecs dot umass.edu
2020-12-08 15:55 ` tkoenig at gcc dot gnu.org
2020-12-08 16:27 ` dpozar at ecs dot umass.edu
2020-12-08 17:36 ` kargl at gcc dot gnu.org
2020-12-08 18:19 ` tkoenig at gcc dot gnu.org
2020-12-08 19:13 ` dpozar at ecs dot umass.edu
2020-12-08 19:27 ` tkoenig at gcc dot gnu.org
2020-12-08 20:46 ` dpozar at ecs dot umass.edu [this message]
2020-12-08 22:06 ` kargl at gcc dot gnu.org
2020-12-09 0:28 ` dpozar at ecs dot umass.edu
2020-12-09 4:38 ` sgk at troutmask dot apl.washington.edu
2020-12-09 13:24 ` dpozar at ecs dot umass.edu
2020-12-09 15:37 ` sgk at troutmask dot apl.washington.edu
2020-12-09 16:04 ` dpozar at ecs dot umass.edu
2021-03-28 12:38 ` dominiq at lps dot ens.fr
2021-03-28 13:05 ` dpozar at ecs dot umass.edu
2021-03-28 13:16 ` dominiq at lps dot ens.fr
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-98201-4-xwChfpX5aI@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: 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).