On 3/6/25 10:02 AM, Steve Kargl wrote:
Andre,
Here's a bit of wordsmith. I removed the abbreviation "Esp."
I'm not sure if there is additional markup needed; especially,
with the "-fcoarray=single" I inserted.
Coarray support has been reworked to allow access to components
in derived typ
PING!
On Thu, 20 Feb 2025 10:54:30 +0100
Andre Vehreschild wrote:
> Hi all,
>
> attached patch makes an attempt to announce the ABI-changes in the coarrays
> library. Me being German always has difficulties to find a proper wording. So
> please propose improvements.
>
> Stupid question: How to I
On Thu, Mar 06, 2025 at 10:49:08PM +0100, Harald Anlauf wrote:
>
> Thanks for the speedy review!
>
It was a bit easier than normal. After I submitted
the PR, I started to poke around in fortran/resolve.cc
to see if I could deal with the issue. I saw that you
grab the PR last night, and left yo
On Thu, Mar 06, 2025 at 10:04:08PM +0100, Harald Anlauf wrote:
>
> this patch fixes an interesting regression that prevented substring
> bounds checks from being generated if the substring start was not a
> variable, but rather a constant or an expression.
>
> The fix I chose turned out to be a l
Andre,
Here's a bit of wordsmith. I removed the abbreviation "Esp."
I'm not sure if there is additional markup needed; especially,
with the "-fcoarray=single" I inserted.
Coarray support has been reworked to allow access to components
in derived types that have not been compiled with coarray
Dear all,
this patch fixes an interesting regression that prevented substring
bounds checks from being generated if the substring start was not a
variable, but rather a constant or an expression.
The fix I chose turned out to be a little larger than I anticipated:
handling the case of an express
