On 10/12/26 11:57 AM, [email protected] wrote:
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find
some details below.
In arm-linux-gnueabihf cross, after:
| commit gcc-17-4941-g4eda76ca63df
| Author: Jerry DeLisle<[email protected]>
| Date: Wed Sep 30 19:26:47 2026 -0700
|
| libgfortran: [PR127684] caf_shmem: SYNC IMAGES hang on terminated image
|
| SYNC IMAGES hung when an image of the image set stopped or failed while
| another image of the set was waiting in the statement.
|
| ... 43 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running gfortran:gfortran.dg/coarray/caf.exp ...
| FAIL: gfortran.dg/coarray/sync_images_failed_1.f90 -fcoarray=lib -pthread
-O2 -lcaf_shmem -lrt execution test
| FAIL: gfortran.dg/coarray/sync_images_stopped_2.f90 -fcoarray=lib -pthread
-O2 -lcaf_shmem -lrt execution test
| FAIL: gfortran.dg/coarray/sync_images_stopped_3.f90 -fcoarray=lib -pthread
-O2 -lcaf_shmem -lrt execution test
Used configuration :
*CI config* tcwg_gnu_cross_check_gcc arm-linux-gnueabihf cross
*configure and test flags:* --target arm-linux-gnueabihf --disable-multilib
--with-float=hard --with-fpu=vfpv3-d16 --with-mode=thumb --with-tune=cortex-a9
--with-arch=armv7-a
Hi,
Thanks for the report. These are not regressions from the patch: the
three tests are new in it, and on this configuration every coarray test
linked with -lcaf_shmem fails at execution, so each newly added one
shows up in the regression delta.
libcaf_shmem starts the images by fork () + execve (argv[0], ...) of the
test executable. Your harness starts the test through qemu-wrapper.sh,
which passes -L <sysroot> to qemu, but the re-executed images are
dispatched by binfmt_misc (arm-binfmt-P) without the sysroot, cannot
find the dynamic loader and exit with status 255. The gfortran.log
should show "arm-binfmt-P: Could not open '/lib/ld-linux-armhf.so.3'"
followed by "ERROR: Image N failed with signal 0, exitstatus 255" for
all images.
Exporting QEMU_LD_PREFIX=<sysroot> in the test environment (in addition
to -L) should fix all of the caf_shmem execution tests; the environment
is passed on to the images. The same happens on your aarch64 cross
configuration.
Regards,
Jerry
