Hi Harald,
my "rant" was more about "Why would one spend time with a library meant for
testing only." I totally agree that the one code base approach is one fine
way to go. I didn't not want to insult anyone and apologize, if I did.
Finally this discussion made me think, what it would need to ha
Am 28.02.25 um 08:24 schrieb Andre Vehreschild:
Hi Thomas,
are you really telling me, that gfortran's coarray test library is compiled for
offloading to GPU (or other SIMD processors)? Because that's what NVPTX is used
for most, right? In my opinion that makes no sense, because coarrays in Fortr
Hi Harald,
thanks for the review. Committed as gcc-15-7747-gc1606e383a3.
Thanks again,
Andre
On Thu, 27 Feb 2025 21:13:08 +0100
Harald Anlauf wrote:
> Hi Andre,
>
> Am 27.02.25 um 18:36 schrieb Andre Vehreschild:
> > Hi all,
> >
> > attached patch fixes user defined finalizers in deriv
No problem, created PR119054 with a reproducer and some details.
Cheers,
Peter
On Thu, 27 Feb 2025 at 20:45, Jerry D wrote:
>
> On 2/27/25 12:33 PM, Peter Hill wrote:
> > On Thu, 27 Feb 2025 at 18:09, Jerry D wrote:
> >>
> >> On 2/27/25 7:38 AM, Peter Hill wrote:
> >>> Dear all,
> >>>
> >>> The
Hi all,
on this regression I had to chew a longer time. Assume this Fortran:
type T
integer, allocatable:: a
end type T
result(type T) function bar()
allocate(bar%a)
end function
call foo([bar()])
That Fortran fragment was translated to something like (pseudo code):
T temp;
T arr[];
temp
Hi Sandra,
thanks for taking on the laborious task. I have browsed over the changes and
found:
Patch 3 in intrinsic.texi:
@@ -2071,6 +2071,9 @@ end program atomic
@cindex Atomic subroutine, ADD with fetch
@table @asis
+@item @emph{Synopsis}:
+@code{CALL ATOMIC_FETCH_ADD (ATOM, VALUE, old [, S
