From: Tobias Burnus <tobias@codesourcery.com>
To: <fortran@gcc.gnu.org>
Cc: Richard Biener <rguenther@suse.de>
Subject: Re: PR fortran/39627 [meta-bug] Fortran 2008 support
Date: Fri, 13 Oct 2023 09:38:53 +0200 [thread overview]
Message-ID: <4638f637-6774-4258-8302-c66405bfe096@codesourcery.com> (raw)
In-Reply-To: <CAFiYyc2TtJqiQkks80_-wg=2vzp6-ysDq6zEDq9fAptJa=N0uw@mail.gmail.com>
On 13.10.23 08:31, Richard Biener 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.
>>
>> ...
>>
>> I am halfway through the F2018 table and will post it on PR85836 when I have done as much as I can.
> Btw, C++ hashttps://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 :/).
Likewise albeit slightly differently for OpenMP,
https://gcc.gnu.org/projects/gomp/#implementation-status
I think we link the C++ page from time to time in release notes at
gcc-*/changes.html.
For Fortran, we also use the wiki – and I do note that we do have a
F2018 page, but not yet a Fortran2023 one:
https://gcc.gnu.org/wiki/Fortran2003Status
https://gcc.gnu.org/wiki/Fortran2008Status
https://gcc.gnu.org/wiki/Fortran2018Status
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2023-10-13 7:38 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 [this message]
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=4638f637-6774-4258-8302-c66405bfe096@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).