forums.silverfrost.com

PaulLaidler · Posted: Fri Nov 18, 2022 5:08 pm Post subject:

John

read80 is -1 for /64 and for this value ISO_FORTRAN_ENV only gives the correct result for /64. This is because at the moment I can't think of a simple way to make read80 correct for both 32 and 64 bits.

read80 = -1 means that 80 bit reals are not available.

integer128 = -1 for both 32 and 64 bit FTN95.

If the compiler was configured by the user (via /config) to make /64 the default then /-64 would revert to the compiler default. In this context it might be helpful to have /32 as an alternative to /-64.

PaulLaidler · Posted: Sat Nov 19, 2022 8:30 am Post subject:

John

This issue has now been resolved. ISO_FORTRAN_ENV will give the relevant KINDs for both 32 bit and 64 bit FTN95.

/32 has been added as an alternative to /-64.

JohnCampbell · Joined: 16 Feb 2006 Posts: 2584 Location: Sydney

Paul,

Thanks for these changes.

I think that /32 is a good addition, especially for clearer documenting of compile options in my .bat builds.

Also, my test from Fri Nov 18 did not identify "integer_kinds" as being available. Hopefully I did not mis-spell.
Is it available ?

How does /ALT_KINDS work with these ?
( I see that "1.0_K must use the default KIND values"

I will test the next FTN95 version.

PaulLaidler · Posted: Sat Nov 19, 2022 10:07 am Post subject:

integer_kinds was missing and has been added for the next full release.

The KIND values in ISO_FORTRAN_ENV are the native KINDs, not the /ALT_KINDS values. They are constants that are external to the compiler. As things are, they don't change when /ALT_KINDS is used.

PaulLaidler · Posted: Mon Nov 21, 2022 8:05 am Post subject:

FTN95 has been extended so that in future ISO_FORTRAN_ENV will give the correct values for /ALT_KINDS.

PaulLaidler · Posted: Mon Nov 21, 2022 12:52 pm Post subject:

z%re and z%im for complex z (from the 2008 Standard) has been added for the next release of FTN95.

Kenneth_Smith · Posted: Tue Nov 22, 2022 5:03 pm Post subject:

Paul,
Thanks for implementing the 2008 Standard support for complex z. This will be very useful.
Ken

PaulLaidler · Posted: Thu Nov 24, 2022 1:54 pm Post subject:

HYPOT has now been added to FTN95 and the DLLs for the next release.

PaulLaidler · Posted: Wed Nov 30, 2022 2:11 pm Post subject:

simon

The SOURCE keyword (Fortran 2003) for the ALLOCATE statement has now been implemented (for arrays only) and will included in the next release of FTN95.

PaulLaidler · Posted: Mon Dec 05, 2022 9:47 am Post subject:

All of the new 2003 and 2008 features that have been suggested on this thread have now been implemented (at least for the next release of FTN95) with the exception of ASSOCIATE.

Further suggestions are welcome so that the order of implementation can be prioritised, implementing first those features that our users would find most helpful.

Since this thread is now rather long, please start a new post for any further suggestions of this kind.

ASSOCIATE currently has a low priority. FTN95 users who understand and want to employ this feature should present a case for its early implementation.

DanRRight · Posted: Tue Dec 06, 2022 12:28 am Post subject:

So soon this compiler will join this six-pack list to compile this widely used F2003 code of your neighbor university? Here is its Makefile:

Kenneth_Smith · Posted: Thu Jan 05, 2023 12:42 pm Post subject:

Paul, One to look at when you get the opportunity (a very minor issue).

PaulLaidler · Posted: Thu Jan 05, 2023 1:53 pm Post subject:

OK. Thanks.

mecej4 · Joined: 31 Oct 2006 Posts: 1896

There is at least one more situation where a similar spurious warning is given -- parts of expressions wherein a variable name is required by the language rules but only the type of the variable matters. Here is an example:

PaulLaidler · Posted: Thu Jan 05, 2023 5:34 pm Post subject:

mecej4

I will make a note of this.