From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Ian Chivers <ian.d.chivers@gmail.com>,
Jane Sleightholme <jane@fortranplus.co.uk>
Subject: Re: PR fortran/39627 [meta-bug] Fortran 2008 support
Date: Fri, 13 Oct 2023 11:02:57 +0100 [thread overview]
Message-ID: <CAGkQGiLq807xM-jruXv7BjmsbER3wKVW_SVdwx4aYwGK+a3Ubg@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc2TtJqiQkks80_-wg=2vzp6-ysDq6zEDq9fAptJa=N0uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
Hi Richard,
I take the non-compliances to be bugs and so I think that there is value in
posting the table on the meta-bug PR. Once the table is on its way to be
published, I will replace it on the PR with a table containing the partial-
and non-compliances only or raise specific PRs. For the F2018 compliance,
the situation is rather more difficult since gfortran's coverage is so
patchy. Thus far it has taken a lot of work to produce something even
halfway accurate. I would baulk at writing PRs for all the 'P's and 'N's
and so it will have to a table for that.
The gfortran wiki has https://gcc.gnu.org/wiki/Fortran2008Status and
https://gcc.gnu.org/wiki/Fortran2018Status. I will update these pages once
I am entirely sure of the state of each.
Cheers
Paul
On Fri, 13 Oct 2023 at 07:32, Richard Biener <richard.guenther@gmail.com>
wrote:
> On Thu, Oct 12, 2023 at 6:54 PM Paul Richard Thomas
> <paul.richard.thomas@gmail.com> wrote:
> >
> > 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.
>
> Btw, C++ has https://gcc.gnu.org/projects/cxx-status.html on the main
> web pages (though I needed to use google to find it,
> discoverability on our webpage isn't too great :/). Maybe something
> similar can be set up for Fortran
> instead of relying on a bugreport?
>
> Richard.
>
> > Regards
> >
> > Paul
> >
>
prev parent reply other threads:[~2023-10-13 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 16:53 Paul Richard Thomas
2023-10-13 6:31 ` Richard Biener
2023-10-13 7:38 ` Tobias Burnus
2023-10-13 10:02 ` Paul Richard Thomas [this message]
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=CAGkQGiLq807xM-jruXv7BjmsbER3wKVW_SVdwx4aYwGK+a3Ubg@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 \
--cc=richard.guenther@gmail.com \
/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).