[Bug fortran/78797] It is time perhaps to implement -std=f2015

2018-05-17 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

janus at gcc dot gnu.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
   Target Milestone|--- |8.0

--- Comment #10 from janus at gcc dot gnu.org ---
(In reply to Harald Anlauf from comment #8)
> As -std=f2018 will be available in 8.0 and replaces -std=f2015,
> shouldn't this bug be closed?

Yes, gfortran 8 has -std=f2018. Closing.

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2018-01-19 Thread vladimir.fuka at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

Vladimir Fuka  changed:

   What|Removed |Added

 CC||vladimir.fuka at gmail dot com

--- Comment #9 from Vladimir Fuka  ---
(In reply to janus from comment #3)
> (In reply to Paul Thomas from comment #2)
> > I will post the existence of this PR to the list over the weekend togetehr
> > with: ftp://ftp.nag.co.uk/sc22wg5/n1551-n1600/n1579.pdf
> 
> This document describes the new features of Fortran 2003, and I know that
> there is also one for 2008. But what about 2015?

There is one for Fortran 2015 as well. https://doi.org/10.1145/3131212.3131213
I am not sure if there is a non-paywall version.

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2018-01-18 Thread anlauf at gmx dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

Harald Anlauf  changed:

   What|Removed |Added

 CC||anlauf at gmx dot de

--- Comment #8 from Harald Anlauf  ---
As -std=f2018 will be available in 8.0 and replaces -std=f2015,
shouldn't this bug be closed?

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2016-12-15 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

--- Comment #7 from janus at gcc dot gnu.org ---
(In reply to janus from comment #6)
> Ok. Btw, the draft version of the F15 standard linked from the gfortran wiki
> is:
> 
> http://j3-fortran.org/doc/year/15/15-007.pdf
> 
> (from December 2014). Is this the last version, or this there a more recent
> one?

Answering that myself, I just found:

http://j3-fortran.org/doc/year/16/16-007r1.pdf

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2016-12-15 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to paul.richard.tho...@gmail.com from comment #5)
> I do apologise, it seems that Mr Reid did not do his usual update. We
> will have to work from the draft standard itself.

Ok. Btw, the draft version of the F15 standard linked from the gfortran wiki
is:

http://j3-fortran.org/doc/year/15/15-007.pdf

(from December 2014). Is this the last version, or this there a more recent
one?

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2016-12-14 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

--- Comment #5 from paul.richard.thomas at gmail dot com  ---
I do apologise, it seems that Mr Reid did not do his usual update. We
will have to work from the draft standard itself.

Paul

On 14 December 2016 at 20:36, paul.richard.thomas at gmail dot com
 wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797
>
> --- Comment #4 from paul.richard.thomas at gmail dot com  at gmail dot com> ---
> Hi Janus,
>
> Yes there is one - I had it open but somehow provided the link to the
> wrong one...
>
> Paul
>
> On 14 December 2016 at 19:20, janus at gcc dot gnu.org
>  wrote:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797
>>
>> --- Comment #3 from janus at gcc dot gnu.org ---
>> (In reply to Paul Thomas from comment #2)
>>> I will post the existence of this PR to the list over the weekend togetehr
>>> with: ftp://ftp.nag.co.uk/sc22wg5/n1551-n1600/n1579.pdf
>>
>> This document describes the new features of Fortran 2003, and I know that 
>> there
>> is also one for 2008. But what about 2015?
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
> --
> You are receiving this mail because:
> You reported the bug.

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2016-12-14 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

--- Comment #4 from paul.richard.thomas at gmail dot com  ---
Hi Janus,

Yes there is one - I had it open but somehow provided the link to the
wrong one...

Paul

On 14 December 2016 at 19:20, janus at gcc dot gnu.org
 wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797
>
> --- Comment #3 from janus at gcc dot gnu.org ---
> (In reply to Paul Thomas from comment #2)
>> I will post the existence of this PR to the list over the weekend togetehr
>> with: ftp://ftp.nag.co.uk/sc22wg5/n1551-n1600/n1579.pdf
>
> This document describes the new features of Fortran 2003, and I know that 
> there
> is also one for 2008. But what about 2015?
>
> --
> You are receiving this mail because:
> You reported the bug.

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2016-12-14 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

--- Comment #3 from janus at gcc dot gnu.org ---
(In reply to Paul Thomas from comment #2)
> I will post the existence of this PR to the list over the weekend togetehr
> with: ftp://ftp.nag.co.uk/sc22wg5/n1551-n1600/n1579.pdf

This document describes the new features of Fortran 2003, and I know that there
is also one for 2008. But what about 2015?

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2016-12-14 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

--- Comment #2 from Paul Thomas  ---
(In reply to janus from comment #1)
> +1
> 
> Can you remind us which F15 features we have already?
> 
> On https://gcc.gnu.org/wiki/GFortran/News I see:
> * Support for IMPLICIT NONE (external, type).
> * ERROR STOP is now permitted in pure procedures.
> 
> Anything else?

Assumed type and assumed rank(partial). I thought that we had implemented the
RANK intrinsic as well but the Chivers et al. table shows N.

There are rather a lot of features that are obsolete or deleted in F2015:
Labeled DO loops have been redundant since Fortran 90 and are now specified to
be obsolescent. The arithmetic IF statement has been deleted. The EQUIVALENCE
and COMMON statements and the block data program unit have been redundant since
Fortran 90 and are now specified to be obsolescent. The nonblock DO construct
has been deleted. The FORALL is now specified to be obsolescent.

What has been done with intrinsics, I am not sure; eg. has COSHAPE been
implemented?

I will post the existence of this PR to the list over the weekend togetehr
with: ftp://ftp.nag.co.uk/sc22wg5/n1551-n1600/n1579.pdf

Cheers

Paul

[Bug fortran/78797] It is time perhaps to implement -std=f2015

2016-12-13 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797

janus at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2016-12-13
 CC||janus at gcc dot gnu.org
 Ever confirmed|0   |1

--- Comment #1 from janus at gcc dot gnu.org ---
+1

Can you remind us which F15 features we have already?

On https://gcc.gnu.org/wiki/GFortran/News I see:
* Support for IMPLICIT NONE (external, type).
* ERROR STOP is now permitted in pure procedures.

Anything else?