public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Cc: Ian Chivers <ian.d.chivers@gmail.com>,
	Jane Sleightholme <jane@fortranplus.co.uk>
Subject: PR fortran/39627 [meta-bug] Fortran 2008 support
Date: Thu, 12 Oct 2023 17:53:57 +0100	[thread overview]
Message-ID: <CAGkQGi+FVnOrqa4=rSh=ZhamM47oiLZNkch3Xt4MAQv=uOs2_Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

I have posted the version 4 of Ian Chivers and Jane Sleightholme's F2008
compliance table as an attachment to PR39627.

With Harald Anlauf's help it has been updated to correspond to gfortran
13.2. In the previous return for gfortran, a number of lines had not been
filled out at all. This has now been done and a rather rough and ready
testcase providing the "evidence" for compliance or not has also been
posted on the PR.

I would welcome comments/corrections if they are also posted on the PR.

I am halfway through the F2018 table and will post it on PR85836 when I
have done as much as I can. I am out for a week and so this will most
likely happen at the end of October. Jerry DeLisle has helped out with
lines 3.x of this table.

As well as being a reply to Ian and Jane, I hope that the tables and
testcases will serve as a resource for gfortran developers as a more
systematic supplement to the meta-bug dependences.

Regards

Paul

             reply	other threads:[~2023-10-12 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 16:53 Paul Richard Thomas [this message]
2023-10-13  6:31 ` Richard Biener
2023-10-13  7:38   ` Tobias Burnus
2023-10-13 10:02   ` Paul Richard Thomas

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='CAGkQGi+FVnOrqa4=rSh=ZhamM47oiLZNkch3Xt4MAQv=uOs2_Q@mail.gmail.com' \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=ian.d.chivers@gmail.com \
    --cc=jane@fortranplus.co.uk \
    /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).