public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "longb at cray dot com" <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: Wed, 03 Mar 2021 21:59:06 +0000 [thread overview] Message-ID: <bug-95644-4-B8ezQFwT7M@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 #7 from Bill Long <longb at cray dot com> --- Inquiry from the original site: "Does GCC provide a timeline for when they will conform to F2018?"
next prev parent reply other threads:[~2021-03-03 21:59 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 [this message] 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 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-B8ezQFwT7M@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: linkBe 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).