Hi Harald,
>From a very quick perusal of the F2018 standard, I have come to the
tentative conclusion that:
(i) 'real module function realg (arg1, arg2)' is almost certainly a
correct requirement, although both flang-new and gfortran compile happily
without the module attribute; and
(ii) As far as
On Tue, Jul 29, 2025 at 10:29:37PM +0200, Harald Anlauf wrote:
>
> - I am a little confused about the handling of the access specification.
> After the first "public :: g", NAG complains about the
>
> generic, public :: g ...
>
> and only allows
>
> generic :: g ...
>
> Then duplicate pub
On 7/27/2025 8:51 PM, Mikael Morin wrote:
Le 27/07/2025 à 13:46, Yuao Ma a écrit :
On 7/27/2025 7:14 PM, Mikael Morin wrote:
Le 27/07/2025 à 11:37, Yuao Ma a écrit :
On 7/27/2025 5:19 PM, Mikael Morin wrote:
+gfc_charlen_type
+string_split (gfc_charlen_type stringlen, const CHARTYPE *str
On 7/27/25 1:25 PM, Harald Anlauf wrote:
Gesendet: Sonntag, 27. Juli 2025 um 21:18
Von: "Mikael Morin"
An: "Andre Vehreschild"
CC: "Harald Anlauf" , fortran@gcc.gnu.org
Betreff: Re: Add: [Bug fortran/121043] [16 Regression] Tests of OpenCoarray
fail to pass, works on 15.1.1 20250712
Le 27/07/
Hi Paul!
Am 24.07.25 um 08:07 schrieb Paul Richard Thomas:
I forgot to include subroutine tests. Please find attached the patch with
updated testcases.
Paul
On Wed, 23 Jul 2025 at 17:53, Paul Richard Thomas <
paul.richard.tho...@gmail.com> wrote:
Hi All,
The attached implements the F2018 ge
Le 29/07/2025 à 09:01, Paul Richard Thomas a écrit :
I haven't had time to track them down
but there are other places where code has had to be inserted to prevent
non-polymorphic references in a polymorphic way. I wonder if they cannot
be unified at some time?
Are there? gfc_get_class_from_e
Le 29/07/2025 à 08:53, Paul Richard Thomas a écrit :
Hi Mikail,
I apologise for the delay between reviewing this patch and the first.
Some daytime work issues came up that I couldn't ignore.
This addition is fine, does as advertised and is good for mainline.
Oops, sorry thanks for the revi
Hi Mikail,
Yes to this third patch as well. I haven't had time to track them down but
there are other places where code has had to be inserted to prevent
non-polymorphic references in a polymorphic way. I wonder if they cannot be
unified at some time?
All three can be pushed to mainline.
Many th