From: Tobias Burnus <burnus@net-b.de>
To: Mikael Morin <mikael.morin@sfr.fr>
Cc: Janus Weil <janus@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran] gfc_notify_std cleanup
Date: Tue, 17 Jul 2012 19:40:00 -0000 [thread overview]
Message-ID: <5005BF8A.6000503@net-b.de> (raw)
In-Reply-To: <5005BBA7.5030009@sfr.fr>
Mikael Morin wrote:
> On 17/07/2012 12:03, Tobias Burnus wrote:
>> On 07/17/2012 11:42 AM, Janus Weil wrote:
>>> + case GFC_STD_F2008_TS:
>>> + strcat (buffer, " TS 29113:");
>>> + break;
>> That's currently correct. However, there is another post-Fortran 2008
>> Technical Specification in preparation. (Coarray extensions.)* How
>> should be handled? "TS 29113 or TS 12345:"?
>>
> Future extension:?
> To be standardized feature:?
> Bleeding edge stuff:?
Well, those names are nice – until we have Fortran 2015 and Fortran 2020.
> Fortran 2015:?
>
> If they are both in the next standard revision, they have to be under
> the same flag anyway.
Well, they will be in the next standard, however, the goal is to be able
to compile with a -std= flag, which does not include compiler extensions
but those features. I have met a couple of users, who just wanted to
have Fortran 95 + allocatable components/dummy arguments (TR 15581:2001)
and not any Fortran 2003 feature. However, as gfortran doesn't have a
suitable -std=, they had to use -std=f2003.
Okay, for Fortran 2015, that is probably not a problem as it seems as if
only few features will be added. There is not much time according to the
schedule [1], only until mid-2015 – and a lot of time will be spend on
the coarray TS (due: mid-2013). Additionally, there seems to be the
feeling in the committee that one shouldn't move forward too quickly,
given that finding a Fortran 2003 compiler is difficult and having no
compiler with full Fortran 2008. [2]
In that sense, one could rename -std=f2008ts into -std=f2015 and have
the "f2015ts" as alias. But otherwise, Fortran 2008 plus TS and Fortran
2015 are different beasts.
Tobias
[1] ftp://ftp.nag.co.uk/sc22wg5/N1901-N1950/N1925.txt
[2] Especially the UK's position is along those lines
ftp://ftp.nag.co.uk/sc22wg5/N1901-N1950/N1923.pdf
prev parent reply other threads:[~2012-07-17 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 9:42 Janus Weil
2012-07-17 10:03 ` Tobias Burnus
2012-07-17 11:48 ` Janus Weil
2012-07-17 12:50 ` Janus Weil
2012-07-17 13:26 ` Tobias Burnus
2012-07-17 14:45 ` Janus Weil
2012-07-17 18:56 ` Mikael Morin
2012-07-17 20:00 ` Janus Weil
2012-07-17 21:55 ` Janus Weil
2012-07-17 19:25 ` Mikael Morin
2012-07-17 19:40 ` Tobias Burnus [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=5005BF8A.6000503@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=janus@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
/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).