[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-07-13 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

Dominique d'Humieres  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-07-12 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

Dominique d'Humieres  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Last reconfirmed||2020-07-12
 Status|UNCONFIRMED |NEW

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-02-23 Thread thenlich at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

--- Comment #7 from Thomas Henlich  ---
This should have a test-case added, ideally by renaming an already existing
test-case containing Fortran 2018 features to .f18.

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-02-14 Thread thenlich at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

--- Comment #6 from Thomas Henlich  ---
Created attachment 47842
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47842=edit
Proposed patch to add .f18/.F18 suffix

Add .f18 and .F18 to list of recognized filename suffixes to match the most
recent standard Fortran 2018

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-02-13 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

--- Comment #5 from Steve Kargl  ---
On Thu, Feb 13, 2020 at 05:59:18PM +, thenlich at gcc dot gnu.org wrote:
> 
> --- Comment #4 from Thomas Henlich  ---
> Additionally, we could also imply -std=f2018 with the .f18/.F18 suffix. That
> would make them more useful.
> 

That would be a POLA as neither f03 nor f08 imply -std=f2003 or
-std=f2008.  AFAIK, these were added as a simply mnemonic for
the programmer.  By default, we have -std=gnu, which is a garabage
consumer (meaning, here's some code, do whatever it takes to 
compile it).  I think that that was a mistake, but that ship
sailed 15+ years ago.

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-02-13 Thread thenlich at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

Thomas Henlich  changed:

   What|Removed |Added

   Priority|P3  |P5

--- Comment #4 from Thomas Henlich  ---
Additionally, we could also imply -std=f2018 with the .f18/.F18 suffix. That
would make them more useful.

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-02-13 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

--- Comment #3 from Steve Kargl  ---
On Thu, Feb 13, 2020 at 04:40:08PM +, thenlich at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736
> 
> --- Comment #2 from Thomas Henlich  ---
> I don't know why the Fortran compiler doesn't treat all files as free-form
> Fortran source files, unless they have a known extension indicating otherwise.

I suppose it has something to do with the fact that gfortran
will accept languages other than Fortran.

% gfortran9 -o z hello.c 
% ./z
hello

If you're really keen on the idea of adding yet another 
useless extension.  Look in gcc/fortran/lang-specs.h.

In 70 years, when F2090 is released, I'll let the next
generation deal with .F90 and .f90. :-)

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-02-13 Thread thenlich at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

--- Comment #2 from Thomas Henlich  ---
I don't know why the Fortran compiler doesn't treat all files as free-form
Fortran source files, unless they have a known extension indicating otherwise.

[Bug fortran/93736] Add .f18 and .F18 file suffixes

2020-02-13 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93736

kargl at gcc dot gnu.org changed:

   What|Removed |Added

 CC||kargl at gcc dot gnu.org

--- Comment #1 from kargl at gcc dot gnu.org ---
IMHO, this should be closed.  The file naming scheme does not imply a standard.
 It implies fixed-form versus free-form.  It was a mistake to add f03, f08,
etc.