Am 19.10.24 um 10:40 schrieb FX Coudert:
Hi,
As UNSIGNED has been booted off the F202Y list, I think calling it
an extension at this time is fair.
Looks good to me. And yes, calling it an extension is fair.
I apologise, I had missed this piece of information. If UNSIGNED is > not on
track
Hello world,
I have just committed the attached patch as obvious - just recognize
that an UNSIGNED is an error in a complex part.
Fix an ICE with UNSIGNED in match_sym_complex_part.
gcc/fortran/ChangeLog:
PR fortran/117225
* primary.cc (match_sym_complex_part): An UNSIGNED in
Hi,
>> As UNSIGNED has been booted off the F202Y list, I think calling it
>> an extension at this time is fair.
>
> Looks good to me. And yes, calling it an extension is fair.
I apologise, I had missed this piece of information. If UNSIGNED is not on
track to becoming a feature in the next sta
My Fortran project is based on -std=f2008. The GNU Fortran (For GCC version
15.0.0) manual's 8.260 STAT example does not link if -std=f2008 is on the
command line: gfortran -std=f2008 test_stat.f90; ./a.out
The ld error is "undefined reference to `stat_'"
This is with gfortran -version 12.2.0
Hi,
> My Fortran project is based on -std=f2008. The GNU Fortran (For GCC version
> 15.0.0) manual’s 8.260 STAT example does not link if -std=f2008 is on the
> command line: gfortran -std=f2008 test_stat.f90; ./a.out
> The ld error is “undefined reference to `stat_’”
Our doc (https://gcc.gnu.o
Am 19.10.24 um 12:12 schrieb FX Coudert:
Hi Thomas,
Thanks for the clarification. I really hope that it makes it into the standard, > I do not disagree that it is useful, I just really wish we don’t have
to maintain> long-term a lot of nonstandard (or worse,
standard-incompatible) extensions.
Hi Thomas,
Thanks for the clarification. I really hope that it makes it into the standard,
I do not disagree that it is useful, I just really wish we don’t have to
maintain long-term a lot of nonstandard (or worse, standard-incompatible)
extensions. -std=legacy took a lot of ugly work over the
