;gmake check-fortran', and if I use RUNTESTFLAGS='dg.exp=\*unsign\*'
to test the unsigned issue reported earlier, I see
=== gfortran Summary ===
# of expected passes434
# of unsupported tests 6
/home/kargl/gcc/obj/gcc/gfortran version 16.0.0 20250629 (experimental) (GC
Yet, another head scratcher.
../../../gcc/libgfortran/caf/shmem/supervisor.c:235:27: error: 'environ'
undeclared (first use in this function)
235 | for (char **e = environ; *e; ++e, ++n)
| ^~~
I see 'extern char **environ;' in shmem.c. Is this sup
On Sun, Jun 29, 2025 at 07:06:57PM -0700, Steve Kargl wrote:
> On Sun, Jun 29, 2025 at 06:54:53PM -0700, Steve Kargl wrote:
> >
> > /usr/local/bin/ld: cannot find -lcaf_shmem: No such file or directory
> > collect2: error: ld returned 1 exit status
> > compiler exited with status 1
> >
> > The fre
On Sun, Jun 29, 2025 at 06:54:53PM -0700, Steve Kargl wrote:
>
> /usr/local/bin/ld: cannot find -lcaf_shmem: No such file or directory
> collect2: error: ld returned 1 exit status
> compiler exited with status 1
>
> The freshly built gfortran cannot find the libcaf_shmem.a.
>
% find . -name \*li
On Sun, Jun 29, 2025 at 03:30:21PM -0700, Steve Kargl wrote:
> On Sun, Jun 29, 2025 at 11:07:31AM -0700, Steve Kargl wrote:
> > On Sun, Jun 29, 2025 at 10:35:39AM -0700, Steve Kargl wrote:
> > >
> > > === gfortran Summary ===
> > >
> > > # of expected passes73149
> > >
On Sun, Jun 29, 2025 at 11:07:31AM -0700, Steve Kargl wrote:
> On Sun, Jun 29, 2025 at 10:35:39AM -0700, Steve Kargl wrote:
> >
> > === gfortran Summary ===
> >
> > # of expected passes73149
> > # of unexpected failures522
It seems that something is mucking wi
On Sun, Jun 29, 2025 at 08:36:38PM +0200, Andre Vehreschild wrote:
>
> I would do git am pr88076_v1_1.patch or patch -p1 each of the patch files. Then they go where they ought to be.
Thanks. I needed -p1 for v1_5 and v1_6.
> Pro tip: create a new branch before doing the git am, then you can ju
Hi Steve,
I would do git am pr88076_v1_1.patch or patch -p1 each of the patch files. Then they go where they ought to be.
Pro tip: create a new branch before doing the git am, then you can just
switch back to master when desired.
- Andre
Andre Vehreschild * ve...@gmx.de
Am 29. Juni 2025 20:2
On Sun, Jun 29, 2025 at 10:35:39AM -0700, Steve Kargl wrote:
>
> Just applied the 6 patch (with the update part 5). I'm
> seeing a significant increase in the number of failures
> in 'make check-fortran' testing.
>
Just re-applied your patches in the top-level gcc/ directory.
I was expecting mo
On Sun, Jun 29, 2025 at 10:35:39AM -0700, Steve Kargl wrote:
>
> === gfortran Summary ===
>
> # of expected passes73149
> # of unexpected failures522
> # of expected failures 343
> # of unresolved testcases 78
> # of unsupported tests 94
On Thu, Jun 26, 2025 at 10:15:01AM +0200, Andre Vehreschild wrote:
>
> I deem this library fit for educational and research use,
> where small to medium sized problems are researched. I do
> not expect it to support a long term running application,
> because is does not join adjacent blocks in th
On 6/29/25 7:52 AM, Thomas Koenig wrote:
Hi Jerry,
real 0m7.426s
user 0m47.602s
sys 0m42.707s
Do you know if these numbers are for a shared-memory MPI implementation
or a traditional one?
Best regards
Thomas
I believe it is traditional. I was using OpenCoarrays with mpich.
On Tue, Jun 24, 2025 at 03:09:33PM +0200, Andre Vehreschild wrote:
>
> this series of patches (six in total) adds a new coarray backend library to
> libgfortran. The library uses shared memory and processes to implement
> running multiple images on the same node. The work is based on work starte
Hi Jerry,
real 0m7.426s
user 0m47.602s
sys 0m42.707s
Do you know if these numbers are for a shared-memory MPI implementation
or a traditional one?
Best regards
Thomas
14 matches
Mail list logo
