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: Wed, 09 Dec 2020 00:28:49 +0000 [thread overview]
Message-ID: <bug-98201-4-lvWDDMjecb@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 #13 from dpozar at ecs dot umass.edu ---
Ok, I have objdump, and the .exe file. What switch options do I need to use in
objdump?
thanks
________________________________
From: kargl at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
Sent: Tuesday, December 8, 2020 5:06 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 #12 from kargl at gcc dot gnu.org ---
(In reply to dpozar from comment #11)
> Thomas,
>
> that looks good. But I am not sure how to proceed ...
>
> dave
Well, the first thing to do is to use either nm or objdump on the
executable created from the code in comment #1 to determine where
csqrtf() lives.
If csqrtf() is from a Microsoft library, then we're done here and
you need to contact Microsoft.
If csqrtf() is from MingW's libm.a (or libm.so), then we're done
here and you need to contact MingW.
If csqrtf() is from libgfortran.a (or libgfortran.so), then you'll
need to look at gcc/libgfortran/intrinsics/c99_functions.c.
--
You are receiving this mail because:
You reported the bug.
next prev parent reply other threads:[~2020-12-09 0:28 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
2020-12-08 22:06 ` kargl at gcc dot gnu.org
2020-12-09 0:28 ` dpozar at ecs dot umass.edu [this message]
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-lvWDDMjecb@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).