Excerpts from ci_notify(a)linaro.org's message of Februar 27, 2025 7:38 pm:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In master-aarch64, after:
> | commit gcc-15-7709-gc2ece13931d
> | Author: Iain Buclaw <ibuclaw(a)gdcproject.org>
> | Date: Tue Feb 25 21:01:23 2025 +0100
> |
> | libphobos: Generate test files for phobos testsuite
> |
> | Extracts all public unittests from libphobos/src and emits them as
> | standalone tests in the testsuite using the tests_extractor script.
> |
> | ... 132 lines of the commit log omitted.
>
> Produces 1 regressions 10 improvements:
> |
> | regressions.sum:
> | Running libphobos:libphobos.phobos/phobos.exp ...
> | FAIL: libphobos.phobos/std_math_hardware.d execution test
> |
> | improvements.sum:
> | Running libphobos:libphobos.phobos/shared/phobos-shared.exp ...
> | FAIL: libphobos.phobos/shared/std/format/internal/floats.d execution test
> | ... and 10 more
>
This just a test that was already failing, it's been renamed from
std/math/hardware.d to std_math_hardware.d in the logs.
Iain.
Hi,
Sorry for this spurious notification, it seems we had a "disk full"
issue on the build machine.
You can ignore this error message.
Christophe
On Fri, 28 Feb 2025 at 03:12, <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 simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/107194
> | Author: Vladimir Makarov <vmakarov(a)redhat.com>
> | Date: Thu Feb 27 13:43:37 2025 -0500
> |
> | [pushed][PR118940][LRA]: Add a test
> |
> | The following patch adds a test for
> |
> | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118940
> | ... 17 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> 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
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
Sorry for this spurious notification, it seems we had a "disk full"
issue on the build machine.
You can ignore this error message.
Christophe
On Fri, 28 Feb 2025 at 03:06, <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 simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/107213
> | Author: Jan Dubiec <jdx(a)o2.pl>
> | Date: Thu Feb 27 22:42:20 2025 +0100
> |
> | [PATCH] H8/300: PR target/109189 Silence -Wformat warnings on Windows
> |
> | This patch fixes annoying -Wformat warnings when gcc is built
> | on Windows/MinGW64. Instead of %ld it uses HOST_WIDE_INT_PRINT_DEC
> | macro, just like many other targets do.
> | ... 12 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> 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
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
On Tue, Feb 25, 2025 at 03:13:10PM +0000, ci_notify(a)linaro.org wrote:
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_build master-arm, after:
> | gcc patch https://patchwork.sourceware.org/patch/107058
> | Author: Jakub Jelinek <jakub(a)redhat.com>
> | Date: Tue Feb 25 13:31:29 2025 +0100
> |
> | [PATCH] simplify-rtx: Fix up simplify_logical_relational_operation [PR119002]
> |
> | Hi!
> |
> | The following testcase is miscompiled on powerpc64le-linux starting with
> | ... 45 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | af73228fdb2 Fortran: Fix detection of descriptor arrays in coarray [PR107635]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> | # First few build errors in logs:
> | # 00:07:45 /home/tcwg-build/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/floating_to_chars.cc:1306:3: internal compiler error: in reverse_condition, at jump.cc:536
> | # 00:07:46 make[5]: *** [Makefile:587: floating_to_chars.lo] Error 1
> | # 00:07:46 make[4]: *** [Makefile:797: all-recursive] Error 1
> | # 00:07:46 make[3]: *** [Makefile:577: all-recursive] Error 1
> | # 00:07:46 make[2]: *** [Makefile:502: all] Error 2
> | # 00:07:46 make[1]: *** [Makefile:12256: all-target-libstdc++-v3] Error 2
> | # 00:07:46 make: *** [Makefile:1062: all] Error 2
Wonder how is that possible, the patch uses REVERSE_CONDITION on GT and
that is handled by both reverse_condition and
reverse_condition_maybe_unordered.
Can I ask for preprocessed source + cc1plus command line + what -march=
etc. options one needs if it is just implied by configure, so that I can
have a look in a cross-compiler?
I really don't have access to 32-bit arm anymore.
Jakub
Hello,
I seem to have begun receiving CI/CD patch notifications from ci_notify(a)linaro.org. I don't understand them, and they might be premature. I don't want to ignore them, though, if they do matter.
I am supplying a 100,000 line patch, roughly, to add a COBOL front-end to gcc. As of now, there is no libgcobol or gcc/cobol directory in the master branch. The supplied patch came most recently in 14 "easy pieces". To be applied successfully, the patches to the Python scripts that create those directories must be applied first.
The URLs at the end of the mail come up 404. I suppose they are ephemeral. I haven't been able to look at a complete log to understand the basis of the report.
The mail says to ask here, so here I be. Please advise. I'm not subscribed to this list.
Thanks,
--jkl
Begin forwarded message:
Date: Wed, 19 Feb 2025 15:10:38 +0000 (UTC)
From: ci_notify(a)linaro.org
To: jklowden(a)schemamania.org
Subject: [Linaro-TCWG-CI] gcc patch #106762: Failure on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In gcc_build master-aarch64, after:
| gcc patch https://patchwork.sourceware.org/patch/106762
| Author: James K. Lowden <jklowden(a)schemamania.org>
| Date: Tue Feb 18 18:37:13 2025 -0500
|
| [PATCH] COBOL v3: 3/14 80K bld: config and build machinery
|
| From f89a50238de62b73d9fc44ee7226461650ab119d Tue 18 Feb 2025
04:19:10 PM EST | From: "James K. Lowden" <jklowden(a)symas.com>
| Date: Tue 18 Feb 2025 04:19:10 PM EST
| ... 27 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 427386042f0 LoongArch: Use normal RTL pattern instead of UNSPEC for
{x,}vsr{a,l}ri instructions
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe gcc:
| # FAILED
| # First few build errors in logs:
| # 00:03:17 make[1]: *** [Makefile:4720: all-gcc] Error 2
| # 00:03:17 make: *** [Makefile:1063: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe gcc:
| 1
Used configuration :
*CI config* tcwg_gcc_build master-aarch64
*configure and test flags:*
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
*
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar…
The full lists of regressions and improvements as well as configure and
make commands are in
*
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar…
The list of [ignored] baseline and flaky failures are in
*
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar…
Current build :
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar…
Reference build :
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3164/artifac…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_build master-aarch64, after:
| commit glibc-2.41.9000-97-gad9c4c53611
| Author: Carlos O'Donell <carlos(a)redhat.com>
| Date: Thu Feb 13 14:27:55 2025 -0500
|
| manual: Document setlogmask as MT-safe.
|
| setlogmask(3) was made MT-safe in glibc-2.33 with the fix for
| bug 26100.
|
| ... 1 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # init_abe_sysroot:
| 0
| # build_abe glibc -- --disable install:
| # FAILED
| # First few build errors in logs:
| # 00:04:01 make[2]: *** [Makefile:90: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/manual/stamp-summary] Error 1
| # 00:04:01 make[1]: *** [Makefile:470: info] Error 2
| # 00:04:01 make: *** [Makefile:20: info] Error 2
|
| From
| # reset_artifacts:
| -10
| # init_abe_sysroot:
| 0
| # build_abe glibc -- --disable install:
| 1
Used configuration :
*CI config* tcwg_glibc_build master-aarch64
*configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
We track this bug report under https://linaro.atlassian.net/browse/GNU-1515. 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
* https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2500/artif…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2500/artif…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2500/artif…
Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2500/artif…
Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2497/artif…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=ad9c4c536115ba38be3e…
On Thu, Feb 13, 2025 at 9:03 PM <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 gcc_build master-arm, after:
> | 2 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/106412
> | de53b4c527f [PATCH 2/2] x86: Fold sibcall targets into jump table
> | 54322404f4b [PATCH 1/2] x86: Add a pass to fold tail call
> | ... applied on top of baseline commit:
> | 2f33fa09aab Daily bump.
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> | # First few build errors in logs:
> | # 00:05:34 make[2]: *** [Makefile:512: _mulsc3.o] Error 1
This is an arm bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118866
> | # 00:05:34 make[1]: *** [Makefile:14340: all-target-libgcc] Error 2
> | # 00:05:34 make: *** [Makefile:1062: all] Error 2
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
> Used configuration :
> *CI config* tcwg_gcc_build master-arm
> *configure and test flags:* --target arm-linux-gnueabihf
>
> 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
> * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/3189/artifact/ar…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
--
H.J.
On Wed, Feb 12, 2025 at 1:17 PM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
Which version of GCC is your IC using? My patch raises the minimum
GCC version to 12.1.
> In glibc_build master-aarch64, after:
> | glibc patch https://patchwork.sourceware.org/patch/106352
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Wed Feb 12 12:53:09 2025 +0800
> |
> | [PATCH] Raise the minimum GCC version to 12.1 [BZ #32539]
> |
> | For all Linux distros with glibc 2.40 which I can find, GCC 14.2 is used
> | to compile glibc 2.40:
> |
> | ... 52 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 392261a2b6 hurd: Replace char foo[1024] with string_t
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # init_abe_sysroot:
> | 0
> | # build_abe glibc -- --disable install:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # init_abe_sysroot:
> | 0
> | # build_abe glibc -- --disable install:
> | 1
>
> Used configuration :
> *CI config* tcwg_glibc_build master-aarch64
> *configure and test flags:* --target aarch64-linux-gnu
>
> 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
> * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/a…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/a…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/a…
>
> Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/a…
> Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2468/artif…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
--
H.J.
On Sun, Feb 02, 2025 at 10:30:18AM +0000, 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 tcwg_kernel/llvm-master-arm-stable-allyesconfig, after:
> | commit llvmorg-21-init-262-gcff0a460ae86
> | Author: Bill Wendling <morbo(a)google.com>
> | Date: Thu Jan 30 15:36:13 2025 -0800
> |
> | [Clang][counted_by] Refactor __builtin_dynamic_object_size on FAMs (#122198)
> |
> | Refactoring of how __builtin_dynamic_object_size() is calculated for
> | flexible array members (in preparation for adding support for the
> | 'counted_by' attribute on pointers in structs).
> | ... 86 lines of the commit log omitted.
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # build_abe binutils:
> | -9
> | # build_kernel_llvm:
> | -5
> | # build_abe qemu:
> | -2
> | # linux_n_obj:
> | 22473
> |
> | From
> | # reset_artifacts:
> | -10
> | # build_abe binutils:
> | -9
> | # build_kernel_llvm:
> | -5
> | # build_abe qemu:
> | -2
> | # linux_n_obj:
> | 22474
>
> Used configuration :
> tcwg_kernel/llvm-master-arm-stable-allyesconfig
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-1541. 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:
>
>
>
> Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-stable-allyesconfig-…
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-stable-allyesconfig-…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/cff0a460ae864505bc2a064c269ebe5…
Thanks, I think Bill fixed this with
https://github.com/llvm/llvm-project/commit/2eb44aa0a94a8d4230c1c9a0c306af1…
Cheers,
Nathan
Hi,
The detected problem is probably caused by a precision error of floating-point arithmetic by the fast-math flag. No need to investigate. Sorry for the noise.
Thanks.
> 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-21-init-888-gdf1bee03de1c
> | Author: Paul Carabas <paulcaraa(a)gmail.com>
> | Date: Thu Feb 6 02:02:29 2025 +0200
> |
> | [mlir] Add math to LLVM lowering support for missing trigonometric & hyperbolic ops (#125753)
> |
> | The patch adds support for math -> LLVM dialect lowering for TanOp,
> | Sinh, Cosh, Tanh
>
> Produces 1 regressions 2 improvements:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0344 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0344/Fujitsu-Fortran-0344_1090.test
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
> |
> | improvements.sum:
> | Running test-suite:Fujitsu/Fortran/0338 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0338/Fujitsu-Fortran-0338_0146.test
> | ... and 2 more
> | # "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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-1547. 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
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/df1bee03de1cdc1505a4e9dde3ed064…
Thanks for the email,
The regression in 0688_0041 is expected and documented
in https://github.com/llvm/llvm-project/pull/124019. Codegen for that test was
already broken before my patch, we just got luckier with undefined behavior
before my changes.
The regression in 0688_0041 should go away after
https://github.com/llvm/llvm-project/pull/125307.
Please do reach out if you have any questions,
Tom
________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Saturday, February 1, 2025 2:54 PM
To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; Tom Eccles <Tom.Eccles(a)arm.com>
Subject: [Linaro-TCWG-CI] llvmorg-21-init-302-gaeaafce46447: 1 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-O0-debug, after:
| commit llvmorg-21-init-302-gaeaafce46447
| Author: Tom Eccles <tom.eccles(a)arm.com>
| Date: Fri Jan 31 09:35:26 2025 +0000
|
| [mlir][OpenMP][flang] make private variable allocation implicit in omp.private (#124019)
|
| The intention of this work is to give MLIR->LLVMIR conversion freedom to
| control how the private variable is allocated so that it can be
| allocated on the stack in ordinary cases or as part of a structure used
| ... 54 lines of the commit log omitted.
Produces 1 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0688 ...
| FAIL: test-suite :: Fujitsu/Fortran/0688/Fujitsu-Fortran-0688_0041.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-1540. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/439/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/439/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/439/…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/439/…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/438/…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/aeaafce4644788963d9823067e46b50…
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-aarch64, after:
| commit binutils-2_41-release-5595-g99b90c46110
| Author: Andrew Carlotti <andrew.carlotti(a)arm.com>
| Date: Thu Jan 30 19:14:46 2025 +0000
|
| aarch64: Fix fp8 feature dependencies
|
| We agreed with LLVM that we shouldn't enforce the architectural
| dependencies between fp8 muliplication features, so remove them.
|
| ... 3 lines of the commit log omitted.
Produces 76 regressions:
|
| regressions.sum:
| Running g++:g++.target/aarch64/sve2/acle/aarch64-sve2-acle-asm.exp ...
| FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O0 -DSTREAMING_COMPATIBLE -DTEST_FULL (test for excess errors)
| FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O0 -DSTREAMING_COMPATIBLE -DTEST_OVERLOADS (test for excess errors)
| FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O2 -g -DTEST_FULL (test for excess errors)
| FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O2 -g -DTEST_OVERLOADS (test for excess errors)
| ... and 73 more
Used configuration :
*CI config* tcwg_gnu_cross_check_gcc master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
We track this bug report under https://linaro.atlassian.net/browse/GNU-1509. 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
* https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19…
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=99b90c46110df…
Has the bisect somehow failed in this? It's highly unlikely that a test
macro would cause an ICE, unless it somehow exposed a latent bug, which
also seems very unlikely in this context.
Sid
On 2025-01-28 20:48, 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 gcc_check master-arm, after:
> | gcc patch https://patchwork.sourceware.org/patch/105574
> | Author: Siddhesh Poyarekar <siddhesh(a)gotplt.org>
> | Date: Tue Jan 28 12:43:50 2025 -0500
> |
> | [PATCH v3] testsuite/118127: Pass fortran tests on ppc64le for IEEE128 long doubles
> |
> | Denormal behaviour is well defined for IEEE128 long doubles, so don't
> | XFAIL some gfortran tests on ppc64le when configured with the IEEE128
> | long double ABI.
> | ... 13 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 2abc555a80b Daily bump.
>
> Produces 1 regressions 1 improvements:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/dg.exp ...
> | FAIL: gcc.dg/pr41123.c (internal compiler error: in gen_movsf, at config/arm/arm.md:7450)
> |
> | improvements.sum:
> | Running gcc:gcc.dg/dg.exp ...
> | FAIL: gcc.dg/pr41123.c (internal compiler error: in gen_movsf, at /home/tcwg-buildslave/workspace/tcwg_gnu_2/abe/snapshots/gcc.git~master/gcc/config/arm/arm.md:7450)
>
> Used configuration :
> *CI config* tcwg_gcc_check master-arm
> *configure and test flags:* --target arm-linux-gnueabihf
>
> 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
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3358/artifact/ar…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
[AMD Official Use Only - AMD Internal Distribution Only]
Thanks for bringing this to my notice. I have opened upstream issue https://github.com/llvm/llvm-project/issues/123960 to track this. I am working on a fix and will update when a PR is opened.
Thanks
Abid
________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Wednesday, January 22, 2025 6:43 AM
To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com>
Cc: Qadeer, Hafiz Abid <HafizAbid.Qadeer(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-18360-gaf91372b7561: 1 regressions on aarch64
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O0-debug, after:
| commit llvmorg-20-init-18360-gaf91372b7561
| Author: Abid Qadeer <haqadeer(a)amd.com>
| Date: Mon Jan 20 12:03:59 2025 +0000
|
| [flang][debug] Improve handling of cyclic derived types. (#122770)
|
| When `RecordType` is converted to corresponding `DIType`, we cache the
| information to avoid doing the conversion again.
|
| ... 66 lines of the commit log omitted.
Produces 1 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0394 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0394/Fujitsu-Fortran-0394_0031.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-1528. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/382/…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/af91372b75613d5654e68d393477e86…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-aarch64, after:
| commit binutils-2_41-release-5490-g50505c486ed
| Author: Nick Clifton <nickc(a)redhat.com>
| Date: Tue Jan 21 10:48:02 2025 +0000
|
| More updated translations
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| # FAILED
| # build_abe linux:
| # build_abe glibc:
| # build_abe gdb:
| # First few build errors in logs:
| # 00:36:56 make[2]: [Makefile:1835: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
| # 00:36:56 make[2]: [Makefile:1836: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
| # 00:47:24 make[7]: [Makefile:850: stamp-modules-bits] Error 1 (ignored)
| # 02:07:45 make[2]: [/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/ada/gcc-interface/Make-lang.in:995: gnat-install-tools] Error 1 (ignored)
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| 2
| # build_abe linux:
| 4
| # build_abe glibc:
| 5
| # build_abe gdb:
| 6
Used configuration :
*CI config* tcwg_gnu_native_build master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
We track this bug report under https://linaro.atlassian.net/browse/GNU-1505. 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
* https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
Current build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/927/a…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=50505c486ed26…
Hi; I'm wondering if anybody is using QEMU's iwmmxt/xscale emulation
for toolchain testing. (My suspicion is the answer is "no".)
This emulation isn't enabled by default, so to use it you would have
to explicitly select an iwmmxt capable CPU (with -cpu or the QEMU_CPU
environment variable). The relevant CPU types are anything beginning
"pxa" (pxa250, pxa255, pxa260, pxa261, pxa262, pxa270-a0, pxa270-a1,
pxa270, pxa270-b0, pxa270-b1, pxa270-c0, pxa270-c5).
The context for this is that I'm considering deprecate-and-drop
for this emulation. (We already dropped all the system emulation
of boards that use these CPUs, so the only thing remaining is their
support via QEMU's user-mode emulation.) If there's still somebody
using this then I'm OK keeping it in QEMU a bit longer, but if
as I suspect it's all entirely unused then we might as well start
the process of dropping it.
(I'm aware that GCC is in the process of dropping its iwmmxt
codegen support. I also didn't find anything particularly with
a web search with examples of users using it.)
thanks
-- PMM
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-arm, after:
| commit glibc-2.40.9000-770-gc36fc507819
| Author: Malte Skarupke <malteskarupke(a)fastmail.fm>
| Date: Wed Dec 4 07:56:38 2024 -0500
|
| nptl: Remove g_refs from condition variables
|
| This variable used to be needed to wait in group switching until all sleepers
| have confirmed that they have woken. This is no longer needed. Nothing waits
| on this variable so there is no need to track how many threads are currently
| ... 4 lines of the commit log omitted.
Produces 189 regressions:
|
| regressions.sum:
| Running g++:g++.dg/analyzer/analyzer.exp ...
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 12 (test for warnings, line 11)
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 17 (test for warnings, line 10)
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 18 (test for warnings, line 11)
| FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 19 (test for warnings, line 11)
| ... and 192 more
Used configuration :
*CI config* tcwg_gnu_native_check_gcc master-arm
*configure and test flags:* --target arm-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-1504. 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
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1822/…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=c36fc50781995e6758ca…
Hi thanks for the report.
I think it has already been fixed upstream by https://github.com/llvm/llvm-project/pull/122550<https://github.com/llvm/llvm-project/pull/122550?notification_referrer_id=N…>. Please let me know if this was not the case.
Kind regards,
Tom
________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Tuesday, January 14, 2025 10:57 PM
To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; Tom Eccles <Tom.Eccles(a)arm.com>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-17063-g303249c4490a: 9 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 llvmorg-20-init-17063-g303249c4490a
| Author: Tom Eccles <tom.eccles(a)arm.com>
| Date: Wed Jan 8 10:05:21 2025 +0000
|
| [flang][StackArrays] track pointers through fir.convert (#121919)
|
| This does add a little computational complexity because now every
| freemem operation has to be tested for every allocation. This could be
| improved with some more memoisation but I think it is easier to read
| ... 6 lines of the commit log omitted.
Produces 9 regressions:
| Running test-suite:Fujitsu/Fortran/0073 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0073/Fujitsu-Fortran-0073_0018.test
| Running test-suite:Fujitsu/Fortran/0487 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0487/Fujitsu-Fortran-0487_0035.test
| NOEXE: test-suite :: Fujitsu/Fortran/0487/Fujitsu-Fortran-0487_0036.test
| ... and 7 more
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-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-1515. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/303249c4490a7777a744d9afd449b64…
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi,
Florian Hahn and I landed 2 patches for fixing FindLastIV reductions
idiom.
https://github.com/llvm/llvm-project/commit/0e528ac404e13ed2d952a2d83aaf838…https://github.com/llvm/llvm-project/commit/3397950f2d21426c7520d114a125881…
I think those can fix the issue you are facing. Please try them, and let me
know if you still have regression on it.
Mel
On Fri, Dec 13, 2024 at 7:11 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 tcwg_flang_test/main-aarch64-Ofast-sve_vla, after:
> | commit llvmorg-20-init-15150-gb3cba9be41bf
> | Author: Mel Chen <mel.chen(a)sifive.com>
> | Date: Thu Dec 12 16:48:31 2024 +0800
> |
> | [LoopVectorize] Vectorize select-cmp reduction pattern for
> increasing integer induction variable (#67812)
> |
> | Consider the following loop:
> | ```
> | int rdx = init;
> | ... 12 lines of the commit log omitted.
>
> Produces 2 regressions:
> | Running test-suite:Fujitsu/Fortran/0365 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0365/Fujitsu-Fortran-0365_0185.test
> | FAIL: test-suite :: Fujitsu/Fortran/0365/Fujitsu-Fortran-0365_0186.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;openmp;clang-tools-extra"
> -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/bin/clang"
> -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++"
> -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm
> -treat-scalable-fixed-error-as-warning=false -DNDEBUG"
> -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve
> -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm
> -treat-scalable-fixed-error-as-warning=false -DNDEBUG"
> -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve
> -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm
> -treat-scalable-fixed-error-as-warning=false -DNDEBUG"
> -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu
> "$\WORKSPACE/test/test-suite"
>
> We track this bug report under
> https://linaro.atlassian.net/browse/LLVM-1482. 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
> *
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The list of [ignored] baseline and flaky failures are in
> *
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build :
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> Reference build :
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Instruction to reproduce the build :
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit :
> https://github.com/llvm/llvm-project/commit/b3cba9be41bfa89bc0ec212706c6028…
On 2025-01-09 12:16, 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 glibc_build master-aarch64, after:
> | 8 patches in glibc
> | Patchwork URL: https://patchwork.sourceware.org/patch/104425
> | b2d4876946 [PATCH v16 8/8] Linux: Update internal copy of '<sys/rseq.h>'
> | cdd3e61830 [PATCH v16 7/8] nptl: Remove the rseq area from 'struct pthread'
> | a673377e3d [PATCH v16 6/8] nptl: Move the rseq area to the 'extra TLS' block
> | 86803776b0 [PATCH v16 5/8] nptl: Introduce <rseq-access.h> for RSEQ_* accessors
> | 928c07fc09 [PATCH v16 4/8] nptl: add rtld_hidden_proto to __rseq_size and __rseq_offset
> | ... and 3 more patches in glibc
> | ... applied on top of baseline commit:
> | e41aabcc93 tests: Verify inheritance of cpu affinity
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # init_abe_sysroot:
> | 0
> | # build_abe glibc -- --disable install:
> | # FAILED
> | # First few build errors in logs:
> | # 00:00:59 ../csu/libc-tls.c:221:64: error: ‘TLS_TP_OFFSET’ undeclared (first use in this function); did you mean ‘TLS_DTV_OFFSET’?
> | # 00:00:59 make[2]: *** [/home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/sysd-rules:451: /home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/csu/libc-tls.o] Error 1
> | # 00:00:59 make[1]: *** [Makefile:484: csu/subdir_lib] Error 2
> | # 00:00:59 make: *** [Makefile:20: all] Error 2
Is there a way to re-trigger this job on the current master branch without posting a new patchset?
I sent this by mistake before Florian's TLS_TP_OFFSET patch was pushed to master but it is now.
Thanks,
Michael
On Mon, Jan 13, 2025 at 4:42 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 binutils_check master-aarch64, after:
> | 2 patches in binutils
> | Patchwork URL: https://patchwork.sourceware.org/patch/104601
> | 795205673be [PATCH v3 2/4] ld: Document mixing IR and non-IR objects for -r
> | a8d189da9d5 [PATCH v3 1/4] ld: Add lto and none-lto output support for ld -r
> | ... applied on top of baseline commit:
> | 338e0b05d8f Fix grammar in "Debug Names" node of the manual
>
> Produces 1 regressions:
> | Running ld:ld-plugin/plugin.exp ...
> | FAIL: nm --plugin
I can't reproduce it on cfarm185.cfarm.net:
/home/hjl/build/binutils/build-aarch64-linux/ld/../binutils/nm-new
--plugin /home/hjl/build/binutils/build-aarch64-linux/ld/.libs/libldtestplug2.so.0
/home/hjl/git/binutils-gdb/ld/testsuite/ld-plugin/func.c
00000000 T _func
00000000 T func
PASS: nm --plugin
It has GCC 13.3.1. I saw you were using GCC 11.4.0. Please
try GCC 11.5.0.
> Used configuration :
> *CI config* tcwg_binutils_check master-aarch64
> *configure and test flags:* --target aarch64-linux-gnu
>
> 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
> * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/233…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/233…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/233…
>
> Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/233…
> Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2093/ar…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
--
H.J.
Hello everyone.
Is that regression is definitely caused by my patch ?
Best Regards,
Hassnaa.
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Date: Saturday, 28 December 2024 at 5:41 AM
To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Hassnaa Hamdi <Hassnaa.Hamdi(a)arm.com>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-16411-gccfe0de0e1e3: 1 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 llvmorg-20-init-16411-gccfe0de0e1e3
| Author: Hassnaa Hamdi <hassnaa.hamdi(a)arm.com>
| Date: Fri Dec 27 12:42:07 2024 +0000
|
| [LV]: Teach LV to recursively (de)interleave. (#89018)
|
| Currently available intrinsics are only ld2/st2, which don't support interleaving factor > 2.
| This patch teaches the LV to use ld2/st2 recursively to support high
| interleaving factors.
Produces 1 regressions:
| Running test-suite:Fujitsu/Fortran/0341 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0341/Fujitsu-Fortran-0341_0409.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-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-1494. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
Full commit : https://github.com/llvm/llvm-project/commit/ccfe0de0e1e37ed369c9bf89dd0188b…
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_build master-aarch64, after:
| commit glibc-2.40.9000-564-ge79e5c4899e
| Author: DJ Delorie <dj(a)redhat.com>
| Date: Thu Nov 14 15:12:57 2024 -0500
|
| assert: ensure posix compliance, add tests for such
|
| Fix assert.c so that even the fallback
| case conforms to POSIX, although not exactly the same as
| the default case so a test can tell the difference.
| ... 6 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # init_abe_sysroot:
| 0
| # build_abe glibc -- --disable install:
| # FAILED
| # First few build errors in logs:
| # 00:01:09 assert.c:120:14: error: ignoring return value of ‘writev’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
| # 00:01:09 make[2]: *** [../o-iterator.mk:9: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/assert/assert.o] Error 1
| # 00:01:09 assert.c:120:14: error: ignoring return value of ‘writev’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
| # 00:01:09 make[2]: *** [../o-iterator.mk:9: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/assert/assert.os] Error 1
| # 00:01:09 make[1]: *** [Makefile:484: assert/subdir_lib] Error 2
| # 00:01:09 make: *** [Makefile:21: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # init_abe_sysroot:
| 0
| # build_abe glibc -- --disable install:
| 1
Used configuration :
*CI config* tcwg_glibc_build master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
We track this bug report under https://linaro.atlassian.net/browse/GNU-1473. 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
* https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2254/artif…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2254/artif…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2254/artif…
Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2254/artif…
Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2252/artif…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=e79e5c4899e82eff1032…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_kernel/gnu-master-arm-mainline-allnoconfig, after:
| commit binutils-2_41-release-5150-g9f2e3c21f65
| Author: Nick Clifton <nickc(a)redhat.com>
| Date: Thu Dec 19 09:59:11 2024 +0000
|
| Fix the handling or arguments and macro pseudo-variables inside nested assembler macros.
|
| PR 32391
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 557
|
| From
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 618
| # linux build successful:
| all
Used configuration :
tcwg_kernel/gnu-master-arm-mainline-allnoconfig
We track this bug report under https://linaro.atlassian.net/browse/GNU-1470. 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:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-mainline-allnoconfig-…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-mainline-allnoconfig-…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=9f2e3c21f6506…
Thanks for the report!
On Thu, Dec 19, 2024 at 04:05:00AM +0000, 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 tcwg_kernel/llvm-master-aarch64-next-defconfig, after:
> | commit v6.13-rc2-20-gce8fd0500b741
> | Author: Bartosz Golaszewski <bartosz.golaszewski(a)linaro.org>
> | Date: Tue Dec 3 10:19:35 2024 +0100
> |
> | crypto: qce - use __free() for a buffer that's always freed
> |
> | The buffer allocated in qce_ahash_hmac_setkey is always freed before
> | returning to use __free() to automate it.
> |
> | ... 3 lines of the commit log omitted.
I have sent a revert of that change:
https://lore.kernel.org/20241218-crypto-qce-sha-fix-clang-cleanup-error-v1-…
Cheers,
Nathan
On Thu, 19 Dec 2024 at 12:58, <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 gcc_build master-aarch64, after:
> | 4 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/103420
> | 3a8cf3dce8f [PATCH 4/4] aarch64: Add mf8 data movement intrinsics
> | afa8fb3b8b4 [PATCH 3/4] aarch64: Add missing makefile dependency
> | 7120f3c23db [PATCH 2/4] aarch64: Use mf8 instead of f8 in builtin definitions
> | 0cc75ba5a1a [PATCH 1/4] aarch64: Macroise simd_type definitions
> | ... applied on top of baseline commit:
> | b117201385d testsuite: Fix toplevel-asm-1.c failure for riscv
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
Hi Richard,
Since the message is not very clear, your patches break the build.
The log contains these errors:
aarch64-sve2.md: In function ‘insn_code
maybe_code_for_aarch64_cm(rtx_code, machine_mode, int, int)’:
aarch64-sve2.md:7205:12: error:
‘CODE_FOR_aarch64_cmltv8qi_vec_concatz_le_vec_concatz_be’ was not
declared in this scope; did you mean
‘CODE_FOR_aarch64_cmltv8qi_vec_concatz_le’?
(and many other similar entries)
HTH
Christophe
> Used configuration :
> *CI config* tcwg_gcc_build master-aarch64
> *configure and test flags:* --target aarch64-linux-gnu
>
> 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
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/15212/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/15212/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/15212/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/15212/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2917/artifac…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
On Tue, 10 Dec 2024 at 08:48, <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 gcc_check master-arm, after:
> | commit gcc-15-6060-ge4a0157c2397
> | Author: Giuseppe D'Angelo <giuseppe.dangelo(a)kdab.com>
> | Date: Mon Dec 9 02:11:19 2024 +0100
> |
> | libstdc++: port bitwise relocatable away from is_trivial
> |
> | In preparation for the deprecation of is_trivial (P3247R2).
> | "bitwise relocation" (or "trivial relocation" à la P1144/P2786)
> | doesn't need the full-fledged notion of triviality, just checking for a
> | ... 8 lines of the commit log omitted.
>
> Produces 3 regressions:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++11 (test for excess errors)
> | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++17 (test for excess errors)
> | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++26 (test for excess errors)
>
> Used configuration :
> *CI config* tcwg_gcc_check master-arm
> *configure and test flags:* --target arm-linux-gnueabihf
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1456. Please let us know if you have a fix.
Fixed at r15-6073-g4b9e1db1a14dbf
>
> 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
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3141/artifact/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3141/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3141/artifact/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3141/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3140/artifact/ar…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e4a0157c2397c9b582cff71d1…
gfortran.dg/pr112877-1.f90 is
-----------
! { dg-do compile }
! { dg-options "-Os" }
program test
use iso_c_binding, only: c_short
interface
subroutine foo(a) bind(c)
import c_short
integer(kind=c_short), intent(in), value :: a
end subroutine foo
end interface
integer(kind=c_short) a(5);
call foo (a(3))
end
! { dg-final { scan-assembler "movswl\t10\\(%rsp\\), %edi" { target { { *-*-linu
x* *-*-gnu* } && { ! ia32 } } } } }
! { dg-final { scan-assembler "movswl\t-14\\(%ebp\\), %eax" { target { { *-*-lin
ux* *-*-gnu* } && { ia32 } } } } }
----------
Why does it fail
FAIL: gfortran.dg/pr112877-1.f90 -O scan-assembler movswl\t10\\(%rsp\\), %edi
on arm-linux-gnueabihf?
H.J.
---------- Forwarded message ---------
From: <ci_notify(a)linaro.org>
Date: Wed, Dec 4, 2024 at 7:26 PM
Subject: [Linaro-TCWG-CI] 7 patches in gcc: 1 regressions on arm
To: <hjl.tools(a)gmail.com>
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In gcc_check master-arm, after:
| 7 patches in gcc
| Patchwork URL: https://patchwork.sourceware.org/patch/102351
| 97708c5e402 [PATCH v5 7/7] ssa-fre-4.c: Enable for all targets and
adjust scan match
| 9c6ba8e5347 [PATCH v5 6/7] scev-cast.c: Enable for all targets and
adjust scan matches
| d78236fd00e [PATCH v5 5/7] vect-simd-clone-1[6-8][cd].c: Expect
in-branch clones for x86
| a9ef03a445d [PATCH v5 4/7] i386: Adjust apx-ndd.c for frontend
promotion removal
| 14ece135ff9 [PATCH v5 3/7] Use incoming small integer argument
type if possible
| ... and 2 more patches in gcc
| ... applied on top of baseline commit:
| fb64a7b0e1d RISC-V: Add assert for insn operand out of range
access [PR117878][NFC]
Produces 1 regressions:
| Running gfortran:gfortran.dg/dg.exp ...
| FAIL: gfortran.dg/pr112877-1.f90 -O scan-assembler
movswl\t10\\(%rsp\\), %edi
Used configuration :
*CI config* tcwg_gcc_check master-arm
*configure and test flags:* --target arm-linux-gnueabihf
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
* https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10456/artifa…
The full lists of regressions and improvements as well as configure
and make commands are in
* https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10456/artifa…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10456/artifa…
Current build :
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10456/artifa…
Reference build :
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3116/artifact/ar…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
--
H.J.
Should have been reported as follows.
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In tcwg_flang_test/main-aarch64-O0-debug, after:
| commit fujitsu_testsuite#a0e269d5d
| Author: KAWASHIMA Takahiro <t-kawashima(a)fujitsu.com>
| Date: Tue Nov 19 17:58:42 2024 +0900
|
| Update RUN.md
|
| - Change the Flang command name
| - Add a notice about `LD_LIBRARY_PATH`
| - Explain about `NOEXE`
Produces 2 regressions:
| Running test-suite:Fujitsu/Fortran/0106 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0106/Fujitsu-Fortran-0106_0033.test
| NOEXE: test-suite :: Fujitsu/Fortran/0106/Fujitsu-Fortran-0106_0034.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm
"-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra"
-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/bin/clang"
-DCMAKE_CXX_COMPILER="$WORKSPACE/llvm-install/bin/clang++"
-DCMAKE_Fortran_COMPILER="$WORKSPACE/llvm-install/bin/flang-new"
-DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS=
-DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g"
-DCMAKE_CXX_FLAGS_RELEASE="-O0 -g"
-DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON
-DTEST_SUITE_SUBDIRS=Fujitsu "$WORKSPACE/test/test-suite"
We track this bug report under
https://linaro.atlassian.net/browse/LLVM-1451. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/95/a…
The full lists of regressions and improvements as well as configure
and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/95/a…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/95/a…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build :
https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/95/a…
Reference build :
https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/90/a…
Instruction to reproduce the build :
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/fujits…
Full commit : https://github.com/fujitsu/compiler-test-suite/commit/a0e269d5d279c3a0781bb…
On Fri, 29 Nov 2024 at 04:54, <ci_notify(a)linaro.org> wrote:
> [Error replacing 'FILE' - Error processing tokens]
Should have been reported as follows.
Some regressions and some improvements after this commit in fujitsu
testsuite.
Regards,
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 fujitsu_testsuite#471c71be0
| Author: Ichinose, Katsumi <1nose(a)jp.fujitsu.com>
| Date: Wed Nov 27 18:43:38 2024 +0900
|
| Add test programs for the 2024-11 release
Produces 19 regressions:
| Running test-suite:Fujitsu/C/0068 ...
| NOEXE: test-suite :: Fujitsu/C/0068/Fujitsu-C-0068_0113.test
| NOEXE: test-suite :: Fujitsu/C/0068/Fujitsu-C-0068_0115.test
| Running test-suite:Fujitsu/C/0072 ...
| NOEXE: test-suite :: Fujitsu/C/0072/Fujitsu-C-0072_0006.test
| ... and 22 more
141 improvements : | # "NOEXE" means : the test program cannot be compiled
| # "FAIL" means : the execution of the compiled binary failed /
output of the binary differs from the expected one
| Running test-suite:Fujitsu/Fortran/0070 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0070/Fujitsu-Fortran-0070_0185.test
| FAIL: test-suite :: Fujitsu/Fortran/0070/Fujitsu-Fortran-0070_0184.test
| Running test-suite:Fujitsu/Fortran/0080 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0080/Fujitsu-Fortran-0080_0008.test
| ... and 179 more
| # "NOEXE" means : the test program cannot be compiled
| # "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;openmp;clang-tools-extra"
-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/bin/clang"
-DCMAKE_CXX_COMPILER="$WORKSPACE/llvm-install/bin/clang++"
-DCMAKE_Fortran_COMPILER="$WORKSPACE/llvm-install/bin/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 -treat-scalable-fixed-error-as-warning=false -mllvm
-aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG"
-DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1
-msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred
-mllvm -treat-scalable-fixed-error-as-warning=false -mllvm
-aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG"
-DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1
-msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred
-mllvm -treat-scalable-fixed-error-as-warning=false -mllvm
-aarch64-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-1449. 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
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The full lists of regressions and improvements as well as configure
and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build :
https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Reference build :
https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
Instruction to reproduce the build :
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/fujits…
Full commit : https://github.com/fujitsu/compiler-test-suite/commit/471c71be0fe507ecb02b5…
On Thu, 28 Nov 2024 at 17:08, <ci_notify(a)linaro.org> wrote:
> [Error replacing 'FILE' - Error processing tokens]
Hi Alexey,
It seems your patch below causes build failure of 654.roms_s for "-O3 -flto" on aarch64-linux-gnu. Has this been reported already?
Let me know if not, and I'll help with the reporting and reproduction.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 26, 2024, at 12:32, 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 tcwg_bmk-code_vect-cpu2017fast/llvm-aarch64-master-O3_LTO, after:
> | commit llvmorg-20-init-13176-gb8703369daf7
> | Author: Alexey Bataev <a.bataev(a)outlook.com>
> | Date: Fri Nov 22 16:10:17 2024 -0500
> |
> | [SLP] Match poison as instruction with the same opcode
> |
> | Patch allows to vector scalar instruction + poison values as if poisons
> | are instructions with the same opcode. It allows better vectorization of
> | the repeated values, reduces number of insertelement instructions and
> | ... 54 lines of the commit log omitted.
>
> Produces 654.roms_s failed to build:
> | the following benchmarks now fails :
> | - 654.roms_s failed to build
>
> Used configuration :
> Below reproducer instructions can be used to re-build both "first_bad" and "last_good" cross-toolchains used in this bisection. Naturally, the scripts will fail when triggerring benchmarking jobs if you don\'t have access to Linaro TCWG CI.
>
> Configuration:
> - Benchmark: SPEC CPU2017
> - Toolchain: Clang + Glibc + LLVM Linker
> - Version: all components were built from their tip of trunk
> - Target: aarch64-linux-gnu
> - Compiler flags: O3 -LTO
> - Hardware: <unknown>
>
> This benchmarking CI is work-in-progress, and we welcome feedback and suggestions at linaro-toolchain(a)lists.linaro.org . In our improvement plans is to add support for SPEC CPU2017 benchmarks and provide "perf report/annotate" data behind these reports.
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-1448. 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:
>
>
>
> Current build : https://ci.linaro.org/job/tcwg_bmk-code_vect-cpu2017fast--llvm-aarch64-mast…
> Reference build : https://ci.linaro.org/job/tcwg_bmk-code_vect-cpu2017fast--llvm-aarch64-mast…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/b8703369daf777706196ff914c0376c…
The results now produced by flang(-new) for Fujitsu Fortran test 0676_0160 are better than the desired results of the test.
The test uses the SUM intrinsic function to compute the sum of 100 complex numbers. These values are all identical. The new results from the SUM intrinsic function match the value of 100 times this value exactly. The expected value used by the test does not, and perhaps it reflects the result of a compiler using a less accurate summation method than flang is now using.