Hi,
These tests are incorrect.
This is a test program issue, not a Flang compiler issue.
A previous change modified the IF statement in these fixed-form Fortran source files:
https://github.com/fujitsu/compiler-test-suite/commit/0a3f51383d0988ea37e4e…
The modified IF statement exceeds the 72-column limit for fixed-form Fortran:
if( abs(test5(low,upper) - res51) > tolerance .and. test5(low,upper) /= res52 ) then
The source is compiled with:
-ffixed-line-length-72
Therefore, the part of the statement beyond column 72 is truncated when Flang parses the fixed-form source.
This results in unmatched parentheses and causes the compilation error.
Please ignore the mail. We'll update the tests.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信日時: 2026年11月20日 9:04
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; 109837443+makatsuka(a)users.noreply.github.com <109837443+makatsuka(a)users.noreply.github.com>
件名: [Linaro-TCWG-CI] 2025-09-202-g0a3f51383: 2 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit 2025-09-202-g0a3f51383
| Author: makatsuka <109837443+makatsuka(a)users.noreply.github.com>
| Date: Wed Nov 18 16:13:54 2026 +0900
|
| Testset fixes based on Workitem 18638 (#263)
|
| * Allow a +/-3 ULP tolerance for vectorized single-precision SUM results.
|
| Co-authored-by: Masanori Akatsuka <m.akatsuka(a)jp.fujitsu.com>
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0366 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0007.test
| NOEXE: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0011.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2306. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/fujit…
Full commit : https://github.com/fujitsu/compiler-test-suite/commit/0a3f51383d0988ea37e4e…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-arm, after:
| commit glibc-2.44.9000-351-g7510a659b83
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Thu Apr 2 14:01:29 2026 -0300
|
| io: Fix silent readdir failures in ftw/nftw (BZ 33085)
|
| The {n}ftw functions fails to distinguish between the end of a directory
| stream and an read error. The existing implementation treated all
| NULL returns as the end of the stream, silently swallowing file system
| ... 14 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running glibc:io ...
| FAIL: io/tst-ftw-bz33085
Used configuration :
*CI config* tcwg_glibc_check master-arm
*configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-2117. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
Details of the regressions above, from the testsuite logs:
| FAIL: io/tst-ftw-bz33085
| original exit status 1
| error: xwrite.c:32: write of 14 bytes failed after 0: Operation not permitted
| error: 1 test failures
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=7510a659b83bedc45560…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-arm, after:
| commit glibc-2.44.9000-340-g03d6fe4963a
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Tue Nov 3 21:32:47 2026 -0300
|
| linux: Implement mprotect in C (BZ 34917)
|
| On x86_64, x32, and aarch64 the upper half of a register holding a 32-bit
| argument is unspecified, so a valid call can fail, for instance:
|
| ... 16 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running glibc:elf ...
| FAIL: elf/tst-valgrind-smoke
Used configuration :
*CI config* tcwg_glibc_check master-arm
*configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-2110. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
Details of the regressions above, from the testsuite logs:
| FAIL: elf/tst-valgrind-smoke
| original exit status 1
| /usr/bin/valgrind
| /lib/ld-linux-armhf.so.3
| bin: /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/valgrind-test
| ld.so: /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/ld.so
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=03d6fe4963a264b4e1c5…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-arm, after:
| commit glibc-2.44.9000-325-g75ac0c2f0a8
| Author: XiaoLei Wu <wuxiaolei(a)kylinos.cn>
| Date: Tue Nov 3 15:28:16 2026 -0300
|
| nss: Fix getnameinfo NI_IDN memory leak on EAI_OVERFLOW
|
| With NI_IDN, getnameinfo returns EAI_OVERFLOW without freeing the
| allocated name if the host buffer is too small. Use checked_copy
| so that this path also reaches free.
| ... 5 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running glibc:nss ...
| FAIL: nss/mtrace-tst-getnameinfo-idn-leak
| FAIL: nss/tst-getnameinfo-idn-leak
Used configuration :
*CI config* tcwg_glibc_check master-arm
*configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-2103. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
Details of the regressions above, from the testsuite logs:
| FAIL: nss/mtrace-tst-getnameinfo-idn-leak
| original exit status 1
| FAIL: nss/tst-getnameinfo-idn-leak
| original exit status 1
| error: xwrite.c:32: write of 14 bytes failed after 0: Operation not permitted
| error: 1 test failures
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=75ac0c2f0a899c1ae07e…
These tests are incorrect. I'll update the tests.
The issue is caused by an incorrect setting in C/0031/fastmath.cmake.
Among the four tested optimization configurations, only the configuration using -O3 -ffast-math -flto fails.
The relative error tolerances for 0031_0089, 0031_0110, and 0031_0122 had already been corrected in the 20260323 branch on March 30, 2026, and the correction was incorporated into the main branch as part of the 2026-06 release on June 4, 2026.
However, commit 898157e94182d9ad70b9c641be0488e2f8e15e5d removed those relative error tolerance settings from fastmath.cmake.
As a result, the default tolerance for the fast-math configuration, 1.0e-14, is now used. This tolerance is too strict for the numerical differences produced by Clang with -O3 -ffast-math -flto, causing fpcmp-target to fail.
Based on the above, restore the relative error tolerance settings that were removed from C/0031/fastmath.cmake.
Specifically, revert the relevant change introduced by: 898157e94182d9ad70b9c641be0488e2f8e15e5d
This restores the tolerance settings that had previously been added by the correction corresponding to commit 713d97dc.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信日時: 2026年10月31日 20:02
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: 114733434+ohno-fj(a)users.noreply.github.com <114733434+ohno-fj(a)users.noreply.github.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] 2025-09-89-g898157e94: 3 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit 2025-09-89-g898157e94
| Author: ohno-fj <114733434+ohno-fj(a)users.noreply.github.com>
| Date: Wed Sep 16 16:02:10 2026 +0900
|
| Workitem 14427_0031 (for GCC) (#154)
|
| Co-authored-by: ohno <ohno.yasuyuki(a)jp.fujitsu.com>
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0031 ...
| FAIL: test-suite :: Fujitsu/C/0031/Fujitsu-C-0031_0089.test
| FAIL: test-suite :: Fujitsu/C/0031/Fujitsu-C-0031_0110.test
| FAIL: test-suite :: Fujitsu/C/0031/Fujitsu-C-0031_0122.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2301. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/fujit…
Full commit : https://github.com/fujitsu/compiler-test-suite/commit/898157e94182d9ad70b9c…
On 10/31/26 10:55 AM, ci_notify(a)linaro.org 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-5582-gd6d1dedff578
> | Author: Jerry DeLisle<jvdelisle(a)gcc.gnu.org>
> | Date: Sat Oct 24 10:49:03 2026 -0400
> |
> | fortran: [PR126968] ICE for wrongly guessed inferred ASSOCIATE type
> |
> | When an ASSOCIATE selector is a function that has not been parsed yet,
> | primary.cc types the associate name by guessing: it takes the first
> | accessible derived type that has a component of the name being
> | ... 49 lines of the commit log omitted.
>
> Produces 12 regressions:
> |
> | regressions.sum:
> | Running gfortran:gfortran.dg/dg.exp ...
> | FAIL: gfortran.dg/associate_91.f90 -O0 (test for excess errors)
> | UNRESOLVED: gfortran.dg/associate_91.f90 -O0 compilation failed to produce executable
> | FAIL: gfortran.dg/associate_91.f90 -O1 (test for excess errors)
> | UNRESOLVED: gfortran.dg/associate_91.f90 -O1 compilation failed to produce executable
> | ... and 8 more
>
> 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
>
> We track this bug report underhttps://linaro.atlassian.net/browse/GNU-2095. (Require Linaro login) Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask onlinaro-toolchain(a)lists.linaro.org mailing list.
Hi,
Thanks for the report. These associate_91.f90 failures were caused by
the type guess for an inferred ASSOCIATE name depending on the shape of
the symtree, which differs between targets (it also failed with -m32 on
x86_64). It is fixed by:
commit e33129b871c (gcc-17-5743-ge33129b871c)
fortran: [PR126968] Make inferred ASSOCIATE type guess
target-independent
I verified the fix on an arm-linux-gnueabihf cross before pushing.
Please let me know if the failures persist after that commit.
Regards,
Jerry