public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85836] [meta-bug] Fortran 2018 support
Date: Sun, 03 Dec 2023 08:26:32 +0000 [thread overview]
Message-ID: <bug-85836-4-HzBatO2EQz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85836-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 56769
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56769&action=edit
Chivers and Sleightholme compliance table mostly completed
The as yet incomplete entries concern coarray features of which I have no
expertise at all. Likewise, other coarray feature have been filled out by
inspection of the gfortran source code.
"Testcases" for sections 1.x to 6.x follow.
Paul
next prev parent reply other threads:[~2023-12-03 8:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85836-4@http.gcc.gnu.org/bugzilla/>
2020-08-11 14:41 ` dominiq at lps dot ens.fr
2020-09-19 18:47 ` anlauf at gcc dot gnu.org
2022-02-24 20:08 ` anlauf at gcc dot gnu.org
2023-12-03 8:26 ` pault at gcc dot gnu.org [this message]
2023-12-03 8:29 ` pault at gcc dot gnu.org
2023-12-03 8:30 ` pault at gcc dot gnu.org
2023-12-03 8:31 ` pault at gcc dot gnu.org
2023-12-03 8:32 ` pault at gcc dot gnu.org
2023-12-03 8:34 ` pault at gcc dot gnu.org
2023-12-18 21:35 ` anlauf at gcc dot gnu.org
2024-02-13 0:43 ` jvdelisle 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-85836-4-HzBatO2EQz@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).