Hi Harald,
thanks for the review. Committed this and the other patch as
gcc-15-7694-gaf73228fdb2.
Thanks again,
Andre
On Mon, 24 Feb 2025 20:22:17 +0100
Harald Anlauf wrote:
> Hi Andre,
>
> Am 24.02.25 um 16:44 schrieb Andre Vehreschild:
> > Hi Harald,
> >
> > I have added some comment
This series addresses PR 47928, a Fortran documentation issue filed back
in 2011. Quoting from the issue:
"IMHO the order of paragraphs in the intrinsics chapter of the manual
is a bit illogical. For instance, the description comes before the
(strangely named) syntax paragraph, so when the descr
Hi all,
for some recreation after all the coarray stuff, I found this pr cc'ed to me.
Taking a look at it, I figured that using a SAVE_EXPR on the lhs of the
assignment was doing the harm. The data seems to be not written back into the
vector shaped data type (like a complex number in this case).
On 2/25/25 9:18 AM, Andre Vehreschild wrote:
Hi all,
for some recreation after all the coarray stuff, I found this pr cc'ed to me.
Taking a look at it, I figured that using a SAVE_EXPR on the lhs of the
assignment was doing the harm. The data seems to be not written back into the
vector shaped d
In the meantime I found out what is causing the problem. There seems to
be a bug in the connection from gfortran to UCRT (Microsofts universal C
runtime, that ships with Windows 10 and 11). If I switch to a compiler
that uses MSVCRT (Microsoft Visual C runtime, an older library, but
still availabl
On 2/25/25 11:41 AM, Jürgen Bausa wrote:
In the meantime I found out what is causing the problem. There seems to
be a bug in the connection from gfortran to UCRT (Microsofts universal C
runtime, that ships with Windows 10 and 11). If I switch to a compiler
that uses MSVCRT (Microsoft Visual C run
