public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95644] [F2018] IEEE_FMA is missing from the IEEE_ARITHMETIC module
Date: Thu, 30 Dec 2021 00:44:24 +0000	[thread overview]
Message-ID: <bug-95644-4-Yk3oDvhK7x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95644-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95644

--- Comment #13 from kargl at gcc dot gnu.org ---
(In reply to ally.alto.0z from comment #12)
> Bill you say you are a “master engineer” and have 25 years of Fortran
> experience and are a principal member of a Fortran committee.
> 
> Would it be unexpected for someone with that experience to offer a fix
> themselves rather than treating this like a free source of labor for their
> lucrative support contracts?

I'm not Bill.  Bill is employed by Cray to work on the Cray Fortran
compiler.  He has been quite helpful in reporting gfortran issues
found either by Cray or by Cray users.

That said, I see that you forgot to attach the patch that you have
developed to fix this issue.  For the record, the patch in comment 
#9 is mine.

  parent reply	other threads:[~2021-12-30  0:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 16:55 [Bug fortran/95644] New: " longb at cray dot com
2020-06-11 17:50 ` [Bug fortran/95644] " dominiq at lps dot ens.fr
2020-10-02 21:46 ` longb at cray dot com
2020-10-05 19:45 ` [Bug fortran/95644] [F2018] " anlauf at gcc dot gnu.org
2020-10-05 19:50 ` longb at cray dot com
2021-01-22 18:00 ` longb at cray dot com
2021-01-23  3:07 ` jvdelisle at charter dot net
2021-03-03 21:59 ` longb at cray dot com
2021-03-04  0:51 ` kargl at gcc dot gnu.org
2021-03-04  2:04 ` kargl at gcc dot gnu.org
2021-03-04  2:22 ` jvdelisle at gcc dot gnu.org
2021-03-04  4:02 ` sgk at troutmask dot apl.washington.edu
2021-12-30  0:36 ` ally.alto.0z at icloud dot com
2021-12-30  0:44 ` kargl at gcc dot gnu.org [this message]
2021-12-30 16:30 ` fxcoudert at gcc dot gnu.org
2021-12-30 17:15 ` fxcoudert at gcc dot gnu.org
2021-12-31 22:24 ` fxcoudert at gcc dot gnu.org
2022-05-06  8:30 ` jakub at gcc dot gnu.org
2023-05-08 12:21 ` rguenth at gcc dot gnu.org
2023-06-06 12:56 ` fxcoudert at gcc dot gnu.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=bug-95644-4-Yk3oDvhK7x@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).