Hi,
Probably these errors are false detections caused by precision errors in floating-point arithmetic.
Please ignore the mail. We'll update the tests. I apologize for the false detection.
Details are as follows.
The primary purpose of this TP (https://github.com/fujitsu/compiler-test-suite/blob/main/Fortran/0683/0683_…) is to verify OpenMP SIMD reduction.
However, since -fopenmp is not specified, !$omp simd is treated as a comment.
Consequently, we are currently verifying the results of sequential calculations for single-precision complex numbers.
In this TP, we determine whether the result is OK or NG by calculating the size of the complex difference in the accumulation results for single-precision complex numbers.
Due to SLP vectorization, a difference arose in the accumulation results, and the difference between the calculated value and the expected value was 3 ULP in the real part and 5 ULP in the imaginary part.
Consequently, the size of the complex difference is 5.8309517, which exceeds the threshold of 5.0, resulting in an NG.
Since the difference is approximately 5 ULP, it is considered to be within the range of rounding errors associated with single-precision complex integration.
if (abs(ss-result) < 5.0) then
print *, "PASS"
else
print *, ss, abs(ss-result)
endif
Expected values: (-15069242.0, -9596797.00)
Actual values: (-15069245.0, -9596802.00)
Therefore, we make the following two corrections.
・To verify OpenMP SIMD reduction, which is the original objective, specify the -fopenmp option.
・Due to vectorization, a difference of 3 ULP in the real part and 5 ULP in the imaginary part has arisen in the single-precision complex multiplication. In this test, the size of the complex difference is calculated as abs(ss - result)\
, but the current threshold of 5.0 does not allow for a complex difference of 5.8309517. To allow for rounding errors of approximately 5 ULP as complex differences, the threshold will be relaxed from 5.0 to 6.0.
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 年 4 月 30 日 (木曜日) 0:41
宛先: 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>
件名: [Linaro-TCWG-CI] llvmorg-23-init-12953-g1348766d1d68: 1 regression on aarch64
[Some people who received this message don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
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_vla, after:
| commit llvmorg-23-init-12953-g1348766d1d68
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Sat Apr 25 07:27:36 2026 -0400
|
| [SLP]Initial support for non-power-of-2 vectorization
|
| Enables non-power-of-2 vectorization within the SLP tree. The root nodes
| are still required to be power-of-2, will be addressed in a follow-up
| patches.
| ... 4 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0683 ...
| FAIL: test-suite :: Fujitsu/Fortran/0683/Fujitsu-Fortran-0683_0101.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=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -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-2211. 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_vla-…
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_vla-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
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_vla-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/1348766d1d686b8825bdaa2f6638c17…
Typo in this email :
We track this bug report under https://linaro.atlassian.net/browse/GNU-1898
. Please let us know if you have a fix.
On Tue, 5 May 2026 at 23:21, <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-eabi cortex-m55 hard, after:
> | commit gcc-17-277-gc0c911821ba
> | Author: Xi Ruoyao <xry111(a)xry111.site>
> | Date: Sat May 2 02:15:42 2026 +0800
> |
> | testsuite: don't link top-level asm tests as PIE [PR 70150]
> |
> | If these tests are linked as PIE, the linker ends up creating
> runtime
> | text relocation and warns or errors out.
> |
> | ... 8 lines of the commit log omitted.
>
> Produces 3 regressions 3 fixes:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/lto/lto.exp ...
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=1to1 -no-pie
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=cache -no-pie
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=max -no-pie
> |
> | fixes.sum:
> | Running gcc:gcc.dg/lto/lto.exp ...
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=1to1
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=cache
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=max
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb
> -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard
> -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard
> --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto
> qemu-cpu=cortex-m55
>
> We track this bug report under https://linaro.atlassian.net/browse/Please
> specify 'Project' and 'IssueType'.. 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_gnu_embed_check_gcc--master-thumb_m55_h…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
Typo in this email :
We track this bug report under https://linaro.atlassian.net/browse/GNU-1897
. Please let us know if you have a fix.
On Fri, 8 May 2026 at 17:49, <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 bootstrap_build master-aarch64-bootstrap_debug, after:
> | commit gcc-17-383-g1a06a37611e
> | Author: Roger Sayle <roger(a)nextmovesoftware.com>
> | Date: Thu May 7 18:46:37 2026 +0100
> |
> | PR middle-end/122871: Doubleword multiplication improvements
> |
> | This patch resolves PR middle-end/122871 by improving RTL
> expansion of
> | doubleword multiplications. The main change is to synth_mult
> adding
> | support for the case where the constant being multiplied has
> BITS_PER_WORD
> | ... 64 lines of the commit log omitted.
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap_debug:
> | # FAILED
> | # First few build errors in logs:
> | # 00:24:37
> /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/expmed.h:398:61:
> error: array subscript -1 is below array bounds of ‘int [64]’
> [-Werror=array-bounds=]
> | # 00:24:50 make[3]: *** [Makefile:1217: expmed.o] Error 1
> | # 00:24:50 make[2]: *** [Makefile:5182: all-stage2-gcc] Error 2
> | # 00:24:50 make[1]: *** [Makefile:26490: stage2-bubble] Error 2
> | # 00:24:50 make: *** [Makefile:1140: all] Error 2
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap_debug:
> | 1
>
> Used configuration :
> *CI config* tcwg_bootstrap_build master-aarch64-bootstrap_debug
> *configure and test flags:* none, autodetected on
> aarch64-unknown-linux-gnu
>
> We track this bug report under https://linaro.atlassian.net/browse/Please
> specify 'Project' and 'IssueType'.. 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
> *
> http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr…
>
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
Typo in this email :
We track this bug report under https://linaro.atlassian.net/browse/GNU-1896
. Please let us know if you have a fix.
On Thu, 7 May 2026 at 18:52, <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 armv8l-unknown-linux-gnueabihf native, after:
> | commit gcc-17-359-g9a231dbb68ab
> | Author: David Malcolm <dmalcolm(a)redhat.com>
> | Date: Wed May 6 09:57:07 2026 -0400
> |
> | analyzer: add data flow events
> |
> | Analyzer warnings relating to problematic values (e.g. by division
> | by zero) can be difficult for the user to understand.
> |
> | ... 421 lines of the commit log omitted.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/analyzer/analyzer.exp ...
> | FAIL: gcc.dg/analyzer/divide-by-zero-6.c (test for warnings, line 17)
> | FAIL: gcc.dg/analyzer/divide-by-zero-6.c at line 18 (test for
> warnings, line 17)
> | FAIL: gcc.dg/analyzer/divide-by-zero-6.c (test for excess errors)
>
> Used configuration :
> *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard
> --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
> --with-fpu=neon-fp-armv8
>
> We track this bug report under https://linaro.atlassian.net/browse/Please
> specify 'Project' and 'IssueType'.. 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_gcc_check--master-arm-build/builds/1017…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
>
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git