On 7/30/25 18:14, Andre Vehreschild wrote:
Hi Toon,
yes, please keep this coming. I suffered from a catastrophic hardware fault on
last Thursday and only get running again. I will process this as soon as I have
processed the earlier reports.
Regards,
Andre
On Wed, 30 Jul 2025 17:43:28 +0200
Toon Moene <t...@moene.org> wrote:
On 7/28/25 20:27, Toon Moene wrote:
On 7/27/25 14:46, Toon Moene wrote:
Today I updated my random-weather example (https://moene.org/~toon/
random-weather) to fix the problem that two different implementations
of the underlying coarray library might give different result numbers
due to the use of random numbers by setting the seed on each image to
a definite number.
I just ran a build of the gfortran-test branch with checking=all on
aarch64-linux-gnu:
https://gcc.gnu.org/pipermail/gcc-testresults/2025-July/854023.html
and got two test failures:
FAIL: gfortran.dg/coarray/alloc_comp_4.f90 -fcoarray=lib -O2
-lcaf_shmem execution test
FAIL: gfortran.dg/coarray/stopped_images_2.f08 -fcoarray=lib -O2
-lcaf_shmem execution test
In spite of these test failures, it *did* give the same results for my
mock weather forecasting code:
https://moene.org/~toon/random-weather
but - standard disclaimer - this code is quite "simple" as far as
coarrays go - no locks, teams, or "image control statements" other than
sync all and off-image coarray access ...
Kind regards,
--
Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
