Hi Mikael,
You were absolutely right. I looked at the caller and "just didn't get it".
Thanks. I will resubmit when I get back from a business trip.
Cordialement
Paul
On Sat, 27 Jul 2024 at 12:35, Mikael Morin wrote:
> Hello,
>
> Le 27/07/2024 à 11:25, Paul Richard Thomas a écrit :
> > This
On 27 July 2024 21:11:19 CEST, Mikael Morin wrote:
>Le 27/07/2024 à 19:23, rep.dot@gmail.com a écrit :
>> On 22 July 2024 20:53:18 CEST, Mikael Morin wrote:
>>> From: Mikael Morin
>>>
>>> Hello,
>>>
>>> this fixes a null pointer dereference with absent optional dummy passed
>>> as BACK arg
Le 27/07/2024 à 19:23, rep.dot@gmail.com a écrit :
On 22 July 2024 20:53:18 CEST, Mikael Morin wrote:
From: Mikael Morin
Hello,
this fixes a null pointer dereference with absent optional dummy passed
as BACK argument of MINLOC/MAXLOC.
Tested for regression on x86_64-linux.
OK for master
On 22 July 2024 20:53:18 CEST, Mikael Morin wrote:
>From: Mikael Morin
>
>Hello,
>
>this fixes a null pointer dereference with absent optional dummy passed
>as BACK argument of MINLOC/MAXLOC.
>
>Tested for regression on x86_64-linux.
>OK for master?
>
>-- >8 --
>
>Protect the evaluation of BACK w
Hello,
Le 27/07/2024 à 11:25, Paul Richard Thomas a écrit :
This patch is straightforward but I am still puzzled as to why it is
necessary for the particular case. Having looked at all the other chunks
of frontend code involving use renaming, it seems that the process just
works everywhere els
This patch is straightforward but I am still puzzled as to why it is
necessary for the particular case. Having looked at all the other chunks of
frontend code involving use renaming, it seems that the process just works
everywhere else. I tried putting the new code in gfc_find_symtree but it
caused
