Tests for supported Fortran features

Help
1

There is a proposal to add user-filterable tables to fortran-lang.org to show:

  1. The open/close code status
  2. Whether free / academic-free / paid
  3. Supported features (both standard and extensions)

and for tools, what they do - linter / formatter / migrator …

For the supported features we need lists of:

  1. The standard features which are not always fully supported
  2. The non-standard features which may not be supported

The proposal is to publish a simple test for each feature, and tests which stress the feature.
My question is which features should be tested?

For example, for non-standard features we could test:

%val
%ref
STRUCTURE/MAP/UNION
Embedded expressions in format specifications

Suggestions would be most welcome. So also would be test code!

2

I have picked up an old fun project of mine again that does exactly this: small programs to check whether a compiler supports a particular feature. You can find the collection I already have at flibs - a collection of Fortran modules / SVN / [r431] /trunk/chkfeatures. And there is a similar set of programs at flibs - a collection of Fortran modules / SVN / [r431] /trunk/chkdiagnostics that aism at checking the diagnostics capabilities of a compiler/

I intend to bring this all to Github. but I would like to enhance it a bit before doing so.

1 Like
3

@Arjen - many thanks for this. We also have a collection of tests which I need to standardise and create a git-hub repository.

4

Want to cooperate on this? :slight_smile:

5

Yes please!

6

Have you seen my SF repository? I use a small configuration file to generate a big batch file/shell script. That way I can easily control what programs should be compiled and run. It is a rather pedestrian way of achieving this, but it gets the job done. Some more flexibility would be nice, like selecting by some keyword, say only the new stuff for F2023.

What type of infrastructure do you use?

7

I’d like to be involved as well. I don’t have much to offer near-term, but longer term, I hope to be able to add to this.

I’m happy to piggy-back on infrastructure you create. I have a need for doing a lot of cross-implementation testing along these lines.

8

Okay, I will create a simple repository with the stuff I have already on Github. I will add you as contributors. Then we can think of a more sophisticated approach, if necessary, as we go along :slight_smile:

1 Like
9

I have created this repository on Github: GitHub - arjenmarkus/chk-fortran-features: Collection of programs to check compiler capabilities.

It contains the first set of checking programs, at this moment just over 160. More to come.