Le 11/09/2022 à 11:57, FX a écrit :
As a first step, one could check the use rename lists; what's done for
iso_fortran_env can be used as an example.
Yes, but iso_fortran_env is handled entirely in front-end, not through external
files.
That's true, but the standard check doesn't really dep
Hi Mikael,
> As a first step, one could check the use rename lists; what's done for
> iso_fortran_env can be used as an example.
Yes, but iso_fortran_env is handled entirely in front-end, not through external
files.
This is what I plan to do when migrating the IEEE modules to front-end, but it
Le 10/09/2022 à 12:14, FX via Fortran a écrit :
If you have a solution for the standards checking, I’ll add it.
As a first step, one could check the use rename lists; what's done for
iso_fortran_env can be used as an example.
To diagnose the other usages, the check could be put in resolve_sym
> Actuelly, that does not work. gfc_notify_std() should not be used at
> code-generation time, but in matching or setting-up symbols. It is never used
> in trans-* files, so I do not think I should introduce it now.
>
> Any hard objection to committing as it is? In the middle term, I intend to
Hi Thomas,
>> Both of these functions are new with Fortran 2018, could you add
>> a standards version check?
>
> Thanks Thomas, I will do that and post here the commit diff. The check will
> not be perfect, though, because the warning/error cannot be emitted when
> loading the module (because i
Hi,
> Both of these functions are new with Fortran 2018, could you add
> a standards version check?
Thanks Thomas, I will do that and post here the commit diff. The check will not
be perfect, though, because the warning/error cannot be emitted when loading
the module (because it’s in an externa
Hi FX,
Maybe the ping is a bit early, as you know I’m not very active anymore, so I do
not know what are the current policies. In particular, how much leeway do I
have to commit the patch if there is no comment from another maintainer?
I am fairly confident about the code, because I wrote the
ping on that patch from last week
Maybe the ping is a bit early, as you know I’m not very active anymore, so I do
not know what are the current policies. In particular, how much leeway do I
have to commit the patch if there is no comment from another maintainer?
I am fairly confident about the
Hum, slightly amended patch, after checking 32-bit results on another linux
machine.
The test for FMA has been made a bit less strict, because otherwise we have
surprised on 387 arithmetic due to excess precision.
Final patch is attached. Regression-tested on x86_64-pc-linux-gnu, both 32- and
6
Hi,
These functions were added in Fortran 2018:
https://gcc.gnu.org/wiki/Fortran2018Status
When it comes to floating-point and IEEE compliance, gfortran fully implements
the 2003 and 2008 standards. In a series of patch, as time permits, I would
like to add all Fortran 2018 features before the
10 matches
Mail list logo
