On Wed, 26 Mar 2025 at 00:55, <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-aarch64, after:
> | commit gcc-15-8904-ge200f53a555
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Mar 25 13:24:08 2025 +0000
> |
> | libstdc++: Optimize std::vector construction from input iterators [PR108487]
> |
> | LWG 3291 make std::ranges::iota_view's iterator have input_iterator_tag
> | as its iterator_category, even though it satisfies the C++20
> | std::forward_iterator concept. This means that the traditional
> | ... 41 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/tree-ssa/initlist-opt1.C -std=c++26 scan-tree-dump gimple "_M_range_initialize<const char\\* const\\*>"
> | FAIL: g++.dg/tree-ssa/initlist-opt2.C -std=c++26 scan-tree-dump gimple "_M_range_initialize<const char\\* const\\*>"
>
> Used configuration :
> *CI config* tcwg_gcc_check 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-1548. Please let us know if you have a fix.
I have a fix:
--- a/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
+++ b/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
@@ -4,7 +4,7 @@
// { dg-skip-if "requires hosted libstdc++ for string" { ! hostedlib } }
// Test that we do range-initialization from const char *.
-// { dg-final { scan-tree-dump {_M_range_initialize<const char\*
const\*>} "gimple" } }
+// { dg-final { scan-tree-dump {_M_range_initialize_n<const char\*
const\*} "gimple" } }
// { dg-final { scan-tree-dump {static const char.*72} "gimple" } }
#include <string>
>
> 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-aarch64-build/3491/artifac…
> 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-aarch64-build/3491/artifac…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3490/artifac…
>
> 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=e200f53a5556516ec831e6b7a…
Hi,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:22, <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:
> | gcc patch https://patchwork.sourceware.org/patch/109136
> | Author: Hu, Lin1 <lin1.hu(a)intel.com>
> | Date: Tue Mar 25 15:44:51 2025 +0800
> |
> | [PATCH] i386: Add "s_" as Saturation for AVX10.2 Converting Intrinsics.
> |
> | Hi, all
> |
> | This patch aims to add "s_" after 'cvt' represent saturation.
> | ... 21 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
> Used configuration :
> *CI config* tcwg_gcc_build master-aarch64
> *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_gcc_build--master-aarch64-precommit/17123/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/17123/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17123/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/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.
Hi,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:10, <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/109150
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Mar 25 10:24:01 2025 +0000
> |
> | [committed] libstdc++: Cast -1 to size_t in <format> [PR119429]
> |
> | This avoids a runtime error from Clang's annoying -fsanitize=integer
> | (even though it's not undefined and behaves correctly).
> |
> | ... 5 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 4d1b1969566 libstdc++: Fix handling of common cpp20-only ranges for flat sets [PR119415]
>
> 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,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:24, <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:
> | gcc patch https://patchwork.sourceware.org/patch/109141
> | Author: Tobias Burnus <tburnus(a)baylibre.com>
> | Date: Tue Mar 25 10:32:08 2025 +0100
> |
> | [Patch] omp-general.cc: Remove 'if' around call to always 'true' returning function [PR118627]
> |
> | I intent to commit this a bit later today as obvious,
> | unless there are comments.
> |
> | ... 35 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
> Used configuration :
> *CI config* tcwg_gcc_build master-aarch64
> *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_gcc_build--master-aarch64-precommit/17126/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/17126/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/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.
Hi,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:22, <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:
> | gcc patch https://patchwork.sourceware.org/patch/109137
> | Author: Sam James <sam(a)gentoo.org>
> | Date: Tue Mar 25 07:54:09 2025 +0000
> |
> | [PATCH] testsuite: add testcase for recent alias fix
> |
> | r15-7961-gdc47161c1f32c3 fixes a typo in ao_compare::compare_ao_refs
> | but there wasn't a testcase available at the time. Now there is.
> |
> | ... 8 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
> Used configuration :
> *CI config* tcwg_gcc_build master-aarch64
> *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_gcc_build--master-aarch64-precommit/17124/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/17124/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/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.
Hi,
Clang 20 has been released and per libc++ policy we want to remove
support for Clang 18. While testing a patch to remove Clang 18 support
[1] I noticed the ARM buildbots you maintain failed [2] since they use
Clang 18.
Would it be possible to update these bots to Clang 20 or Clang 19?
[1] https://github.com/llvm/llvm-project/pull/130142
[2] https://buildkite.com/llvm-project/libcxx-ci/builds/41081
Kind regards,
Mark
Hi,
We have encountered a CI failure on a libc++ CI bot owned by this list. I
am seeking assistance to help debug the issue since it's a bit difficult to
do without having access to that platform. This is time sensitive for us,
since the patch fixes a real issue we encountered and we'd like to get it
fixed in the LLVM 20 release. See
https://github.com/llvm/llvm-project/pull/131921#issuecomment-2737539434
for more details.
Thanks,
Louis
On 21/03/2025 20:36, 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-8649-g1d2257dc850
> | Author: Richard Earnshaw <rearnsha(a)arm.com>
> | Date: Fri Mar 21 15:20:03 2025 +0000
> |
> | arm: testsuite: make unaligned-memcpy-*.c executable tests [PR91614]
> |
> | These tests have been looking for a very specific instruction sequence
> | which has the tendency to be fairly unstable as a result. But what is
> | more interesting is that the the tests must not contain instructions
> | ... 22 lines of the commit log omitted.
>
> Produces 1 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/unaligned-memcpy-4.c scan-assembler-not unaligned
Should be fixed now. The scanner was matching 'unaligned' in a .file directive containing the test name.
R.
>
> Used configuration :
> *CI config* tcwg_gcc_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1545. 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_gcc_check--master-arm-build/3580/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/3580/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3579/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=1d2257dc850d088f6d9267b46…
Hello there,
You had previously warned me of the problem with the pre-commit patch, from
which I was able to identify the problem. Unfortunately, I screwed up by
only correcting the cast of 'dim' in three out of four places. Hans-Peter
Nilsson has put it right and I believe that the regression will disappear.
Thanks for your help on this.
Paul
On Sun, 16 Mar 2025 at 13: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 arm-eabi cortex-m23 soft, after:
> | commit gcc-15-8035-g7ee31bc9276
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Mar 13 13:34:55 2025 +0000
> |
> | libstdc++: Implement <stdbit.h> for C++26 (P3370R1)
> |
> | This is the first part of the P3370R1 proposal just approved by the
> | committee in Wrocław. This adds C++ equivalents of the functions added
> | to C23 by WG14 N3022.
> | ... 16 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors)
> | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to produce executable
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1543. Please let us know if you have a fix.
All the errors are of the form:
error: 'ULLONG_MAX' was not declared in this scope
but the test includes <limits.h>.
So this target doesn't support long long? Or just doesn't define ULLONG_MAX?
Hi,
Sorry for this issue, I've reverted this in:
https://github.com/llvm/llvm-project/commit/21610e3ecc8bc727f99047e544186b3…
Before I start digging into it further, could you please let me know
what hardware is used to run these tests? I just thought I'd
double-check that the requested -msve-vector-bits=256 does match the
hardware SVE length.
Thanks very much,
Ricardo
On 3/7/25 09:03, ci_notify(a)linaro.org wrote:
> [You 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_vls-lto-lld, after:
> | commit llvmorg-21-init-4020-gf01e760c0836
> | Author: Ricardo Jesus <rjj(a)nvidia.com>
> | Date: Thu Mar 6 09:27:07 2025 +0000
> |
> | [AArch64][SVE] Improve fixed-length addressing modes. (#129732)
> |
> | When compiling VLS SVE, the compiler often replaces VL-based offsets
> | with immediate-based ones. This leads to a mismatch in the allowed
> | addressing modes due to SVE loads/stores generally expecting immediate
> | ... 29 lines of the commit log omitted.
>
> Produces 6235 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/C/0000 ...
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0003.test
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0004.test
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0008.test
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0009.test
> | ... and 6513 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=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -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-1592 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_vls-lto-l…>> 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_vls-lto-l…>> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/>>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>>
> 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/f01e760c08365426de95f02dc2c2dc6…>
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_kernel/gnu-master-aarch64-lts-defconfig, after:
| commit gcc-15-8025-g7dae3f64c069
| Author: Richard Sandiford <richard.sandiford(a)arm.com>
| Date: Thu Mar 13 12:03:04 2025 +0000
|
| match.pd: Fold ((X >> C1) & C2) * (1 << C1)
|
| Using a combination of rules, we were able to fold
|
| ((X >> C1) & C2) * (1 << C1) --> X & (C2 << C1)
| ... 22 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 8743
|
| From
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 10059
| # linux build successful:
| all
| # linux boot successful:
| boot
Used configuration :
tcwg_kernel/gnu-master-aarch64-lts-defconfig
We track this bug report under https://linaro.atlassian.net/browse/GNU-1539. 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-aarch64-lts-defconfig-bui…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
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=7dae3f64c069b942b9abd768f…
On Sun, 2 Mar 2025 at 02:42, <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-m7 hard, after:
> | commit gcc-15-7765-g3866ca796d5
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Feb 27 13:27:17 2025 +0000
> |
> | libstdc++: Fix ranges::move and ranges::move_backward to use iter_move [PR105609]
> |
> | The ranges::move and ranges::move_backward algorithms are supposed to
> | use ranges::iter_move(iter) instead of std::move(*iter), which matters
> | for an iterator type with an iter_move overload findable by ADL.
> | ... 16 lines of the commit log omitted.
>
> Produces 8 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 25_algorithms/move/constrained.cc -std=gnu++20 (test for excess errors)
> | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++20 compilation failed to produce executable
> | FAIL: 25_algorithms/move/constrained.cc -std=gnu++26 (test for excess errors)
> | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++26 compilation failed to produce executable
> | ... and 4 more
It looks like thumb has some unusual linking requirements that I'm not
familiar with, so undefined functions (which are never actually called
in the test) cause linker errors:
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
undefined reference to `pr105609::iter_move(pr105609::I const&)'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZN8pr1056099iter_moveERKNS_1IE): Unknown destination type
(ARM/Thumb) in /tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
dangerous relocation: unsupported relocation
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
undefined reference to `pr105609::I::operator++()'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZN8pr1056091IppEv): Unknown destination type (ARM/Thumb) in
/tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
dangerous relocation: unsupported relocation
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
undefined reference to `pr105609::I::operator==(pr105609::I) const'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZNK8pr1056091IeqES0_): Unknown destination type (ARM/Thumb) in
/tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
dangerous relocation: unsupported relocation
I think I should be able to workaround this.
On Thu, 6 Mar 2025 at 23:55, Giuseppe D'Angelo via Gcc-regression
<gcc-regression(a)gcc.gnu.org> wrote:
>
> On 06/03/2025 20:29, ci_notify(a)linaro.org wrote:
> > Dear contributor,
> >
> > Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> This has been fixed on trunk by r15-7863-gd2b022e38a778d.
>
Indeed I can see the test now passes.
Thanks,
Christophe
> Thank you,
> --
> Giuseppe D'Angelo
Hello,
I have recived the email quoted below. I wonder how my patch could have
caused an issue when the only file it touches is related to H8/300
target, not ARM. As far as I can see in the logs you are not building an
H8/300 toolchain.
Best regards,
/J.D.
PS. I am not subscribed so please CC me.
-------- Forwarded Message --------
Subject: [Linaro-TCWG-CI] gcc patch #107213: Failure on aarch64
Date: Fri, 28 Feb 2025 02:06:28 +0000 (UTC)
From: ci_notify(a)linaro.org
Reply-To: linaro-toolchain(a)lists.linaro.org
To: jdx(a)o2.pl
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.
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.
Should have been reported as below.
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-13009-g3f594741cf8e
| Author: Peter Klausler <pklausler(a)nvidia.com>
| Date: Thu Nov 21 10:47:21 2024 -0800
|
| [flang] Fix implementation of Kahan summation (#116897)
|
| In the runtime's implementation of floating-point SUM, the
| implementation of Kahan's algorithm for increased precision is
| incorrect. The running correction factor should be subtracted from
each
| ... 4 lines of the commit log omitted.
Produces 1 regressions1 improvements:
| Running test-suite:Fujitsu/Fortran/0676 ...
| FAIL: test-suite :: Fujitsu/Fortran/0676/Fujitsu-Fortran-0676_0160.test
| # "FAIL" means : the execution of the compiled binary failed / output
of the binary differs from the expected one
| Running test-suite:Fujitsu/Fortran/0366 ...
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0097.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-1446.
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/3f594741cf8e1537fb25f84ef3cf224…
It should have been reported as below. This is after this commit in
llvm-test-suite.
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-19.1.1-16-g9f743a87e
| Author: KAWASHIMA Takahiro <t-kawashima(a)fujitsu.com>
| Date: Fri Nov 22 10:41:14 2024 +0900
|
| [cmake] Support more Fortran filename suffixes (#180)
|
| These Fortran suffixes are aligned with the `lookupTypeForExtension`
| function in `clang/lib/Driver/Types.cpp`.
Produces 30 regressions:
| Running test-suite:Fujitsu/Fortran/0647 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0001.test
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0002.test
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0004.test
| NOEXE: test-suite :: Fujitsu/Fortran/0647/Fujitsu-Fortran-0647_0006.test
| ... and 27 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 -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-1447. 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_t…
Full commit : https://github.com/llvm/llvm-test-suite/commit/9f743a87e20346070725bd1f06cc…
On Sat, 23 Nov 2024 at 11:20, <ci_notify(a)linaro.org> wrote:
> [Error replacing 'FILE' - Error processing tokens]
This report should have been as below.
We are checking what went wrong on our side.
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-12914-g5d38e6e42a90
| Author: Ivan R. Ivanov <ivanov.i.aa(a)m.titech.ac.jp>
| Date: Wed Nov 20 10:49:34 2024 +0900
|
| [flang] Introduce hlfir.elemental lowerings to
omp.workshare_loop_nest (#104748)
|
| This patch adds parallelization support for the following
expression in OpenMP
| workshare constructs:
|
| ... 3 lines of the commit log omitted.
Produces 32 regressions:
| Running test-suite:Fujitsu/Fortran/0398 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0000.test
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0001.test
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0002.test
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0003.test
| ... and 28 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 -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-1444. 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/5d38e6e42a90f5d469b5ff9e25e5e88…
On Thu, 21 Nov 2024 at 14:39, <ci_notify(a)linaro.org> wrote:
> [Error replacing 'FILE' - Error processing tokens]
Hi Sergei,
It seems your patch below breaks build of several SPEC CPU2017 benchmarks on 32-bit ARM.
Could you please investigate? Please let me know if you need any assistance in reproducing build failures.
Thanks,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 21, 2024, at 20:22, 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-cpu2017rate/llvm-arm-master-O3, after:
> | commit llvmorg-20-init-12823-g8c56dd3040f2
> | Author: Sergei Barannikov <barannikov88(a)gmail.com>
> | Date: Wed Nov 20 16:07:05 2024 +0300
> |
> | [ARM] Stop gluing FP comparisons to FMSTAT (#116676)
> |
> | Following #116547, this changes the result of `ARMISD::CMPFP*` and the
> | operand of `ARMISD::FMSTAT` from a special `Glue` type to a normal type.
> |
> | ... 20 lines of the commit log omitted.
>
> Produces 544.nab_r failed to build:
> | the following benchmarks now fails :
> | - 544.nab_r failed to build
> | - 538.imagick_r failed to build
> | - 526.blender_r failed to build
> | - 525.x264_r 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: arm-linux-gnueabihf
> - Compiler flags: O3
> - 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-1443. 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-cpu2017rate--llvm-arm-master-O…
> Reference build : https://ci.linaro.org/job/tcwg_bmk-code_vect-cpu2017rate--llvm-arm-master-O…
>
> 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/8c56dd3040f295874e3d5742b5dfc10…
This report should have been as per below. We'll investigate what went wrong.
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-12768-g40c8938ff844
| Author: Ivan R. Ivanov <ivanov.i.aa(a)m.titech.ac.jp>
| Date: Wed Nov 20 10:49:34 2024 +0900
|
| [flang] Introduce hlfir.elemental lowerings to omp.workshare_loop_nest (#104748)
|
| This patch adds parallelization support for the following expression in OpenMP
| workshare constructs:
|
| ... 1 lines of the commit log omitted.
Produces 32 regressions:
| Running test-suite:Fujitsu/Fortran/0398 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0000.test
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0001.test
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0002.test
| NOEXE: test-suite :: Fujitsu/Fortran/0398/Fujitsu-Fortran-0398_0003.test
| ... and 28 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-1441. 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/40c8938ff8447fc46bd2aa1605e3147…
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 21, 2024, at 03:10, ci_notify(a)linaro.org wrote:
>
> [Error replacing 'FILE' - Error processing tokens]
Hi there,
I can only locate the error message like "/tmp/cc4i9dn1.s:151930: Error: conditional branch out of range".
But failed to reproduce this when cross build, is there anywhere to get the build option for reproducing?
Thanks.
Pan
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Sunday, October 27, 2024 9:58 AM
To: Li, Pan2 <pan2.li(a)intel.com>
Cc: gcc-regression(a)gcc.gnu.org
Subject: [Linaro-TCWG-CI] gcc-15-4672-gdf4af89bc3e: Failure on arm
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1389 , please let us know if you are looking at the problem and/or when you have a fix.
In bootstrap_build master-arm-bootstrap_profiled after:
| commit gcc-15-4672-gdf4af89bc3e
| Author: Pan Li <pan2.li(a)intel.com>
| Date: Thu Oct 24 21:57:04 2024 +0800
|
| Match: Simplify branch form 3 of unsigned SAT_ADD into branchless
|
| There are sorts of forms for the unsigned SAT_ADD. Some of them are
| complicated while others are cheap. This patch would like to simplify
| the complicated form into the cheap ones. For example as below:
| ... 65 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe bootstrap_profiled:
# FAILED
# First few build errors in logs:
# 01:33:58 make[3]: *** [Makefile:1195: gimple-match-1.o] Error 1
# 01:33:58 make[2]: *** [Makefile:5220: all-stageprofile-gcc] Error 2
# 01:33:58 make[1]: *** [Makefile:26089: stageprofile-bubble] Error 2
# 01:33:58 make: *** [Makefile:26343: profiledbootstrap] Error 2
From
# reset_artifacts:
-10
# true:
0
# build_abe bootstrap_profiled:
1
The configuration of this build is:
CI config tcwg_bootstrap_build master-arm-bootstrap_profiled
configure and test flags: --target arm-linux-gnueabihf
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil…
Reference build : https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil…
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=df4af89bc3eabbeaccb16539a…
Hello,
Function multi versioning is a nice feature for developers to target certain architecture features easily. [1][2]
This patch enables it for Windows too in Clang ( already supported on Linux, Android, Darwin ):
https://github.com/llvm/llvm-project/pull/111962
Please help with the review, and also happy to answer questions if you have.
Thanks,
Daniel
[1] https://github.com/ARM-software/acle/blob/main/main/acle.md#function-multi-…
[2] https://learn.arm.com/learning-paths/cross-platform/function-multiversionin…
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.
On Fri, Nov 01, 2024 at 06:57:21AM +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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
All the logs seem to be truncated?
What kind of failure is this? Is it a problem on the builder?
Thanks,
-Andi
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In gcc_build master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/99988
> | Author: Andi Kleen <ak(a)gcc.gnu.org>
> | Date: Thu Oct 31 16:19:16 2024 -0700
> |
> | [PATCH] Enable autofdo bootstrap for lto/fortran
> |
> | When autofdo bootstrap support was originally implemented there were
> | issues with the LTO bootstrap, that is why it wasn't enabled
> | for them. I retested this now and it works on x86_64-linux.
> | ... 10 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | f8ae2cce23fc Support Intel AMX-MOVRS
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> 1
>
> The configuration of this build is:
> *CI config* tcwg_gcc_build master-aarch64
> *configure and test flags:* --target aarch64-linux-gnu
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/13759/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2726/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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1403 , please let us know if you are looking at the problem and/or when you have a fix.
In glibc_check master-aarch64 after:
| commit glibc-2.40.9000-287-g5c22fd25c15
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Fri Oct 25 15:21:48 2024 -0300
|
| math: Use exp2m1f from CORE-MATH
|
| The CORE-MATH implementation is correctly rounded (for any rounding mode)
| and shows better performance compared to the generic exp2m1f.
|
| ... 41 lines of the commit log omitted.
FAIL: 2 regressions
regressions.sum:
| === glibc tests ===
|
| Running glibc:math ...
| FAIL: math/test-float-exp2m1
| FAIL: math/test-float32-exp2m1
|
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2032/artif…
Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/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=5c22fd25c15ff56583ca…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1401 , please let us know if you are looking at the problem and/or when you have a fix.
In glibc_check master-aarch64 after:
| commit glibc-2.40.9000-286-g5fa89852fa1
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Fri Oct 25 15:21:47 2024 -0300
|
| math: Use exp10m1f from CORE-MATH
|
| The CORE-MATH implementation is correctly rounded (for any rounding mode)
| and shows better performance compared to the generic exp10m1f.
|
| ... 33 lines of the commit log omitted.
FAIL: 2 regressions
regressions.sum:
| === glibc tests ===
|
| Running glibc:math ...
| FAIL: math/test-float-exp10m1
| FAIL: math/test-float32-exp10m1
|
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
The configuration of this build is:
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2029/artif…
Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2028/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=5fa89852fa12fe56c315…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1398 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit v9.1.0-1163-ga3c3345cac
| Author: Akihiko Odaki <akihiko.odaki(a)daynix.com>
| Date: Tue Oct 29 12:54:43 2024 +0000
|
| scripts/symlink-install-tree.py: Fix MESONINTROSPECT parsing
|
| The arguments in MESONINTROSPECT are quoted with shlex.quote() so it
| must be parsed with shlex.split(). Otherwise the script will fail if
| the build directory has a character like "~" in it.
| ... 21 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
7
The configuration of this build is:
*CI config* tcwg_gnu_cross_build master-aarch64
*configure and test flags:* --target aarch64-linux-gnu
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/888/ar…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/887/ar…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s…
Full commit : https://gitlab.com/qemu-project/qemu/commit/a3c3345cac7d2f9cc827d7ecce91579…
On Wed, Oct 30, 2024 at 06:06:06AM +0000, ci_notify(a)linaro.org wrote:
> In CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig after:
>
> | commit llvmorg-20-init-10266-g71315698c91d
> | Author: serge-sans-paille <sguelton(a)mozilla.com>
> | Date: Mon Oct 28 20:40:52 2024 +0000
> |
> | [clang] Warn about memset/memcpy to NonTriviallyCopyable types (#111434)
> |
> | This implements a warning that's similar to what GCC does in that
> | context: both memcpy and memset require their first and second operand
> | to be trivially copyable, let's warn if that's not the case.
Thanks for the report, this should be fixed in tip of tree now:
https://github.com/llvm/llvm-project/commit/dc56a86b96d77a93f761995d50f7b2f…
Cheers,
Nathan
ci_notify(a)linaro.org writes:
> Dear contributor, our automatic CI has detected problems related to
> your patch(es). Please find some details below. If you have any
> questions, please follow up on linaro-toolchain(a)lists.linaro.org
> mailing list, Libera's #linaro-tcwg channel, or ping your favourite
> Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or
> reproduce the issue locally. If you can't get what you need from our
> CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1388 , please let us know if you are looking at the problem and/or when you have a fix.
Should be fixed with r15-4692-g40fedaf35fa99a9728d5b84d47035f4c92e1ba90.
thanks,
sam
Hi Linaro Toolchain Team,
I got this regression email for one of my patch but failure does not look like related to the change. Also this look like a false positive to me as test is failing in baseline also.
From the logs regression is shown in
| Running gdb:gdb.cp/nextoverthrow.exp ...
| FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
But the baseline file also has the same failure in sum file and somehow not shown in xfail file:
The list of [ignored] baseline and flaky failures are in
https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
Thanks & Best Regards
Abdul Basit
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Saturday, October 26, 2024 4:29 AM
To: Ijaz, Abdul B <abdul.b.ijaz(a)intel.com>
Subject: [Linaro-TCWG-CI] gdb patch #99582: FAIL: 1 regressions on arm
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
In gdb_check master-arm after:
| gdb patch https://patchwork.sourceware.org/patch/99582
| Author: Ijaz, Abdul B <abdul.b.ijaz(a)intel.com>
| Date: Fri Oct 25 16:37:46 2024 +0200
|
| [PATCH v8 1/1] fortran: Fix arrays of variable length strings for FORTRAN
|
| Before this change resolve_dynamic_array_or_string was called for
| all TYPE_CODE_ARRAY and TYPE_CODE_STRING types, but, in the end,
| this function always called create_array_type_with_stride, which
| ... 65 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 3d17c881721 [gdb] Handle bad alloc in gdb_rl_callback_read_char_wrapper_noexcept
FAIL: 1 regressions
regressions.sum:
| === gdb tests ===
|
| Running gdb:gdb.cp/nextoverthrow.exp ...
| FAIL: gdb.cp/nextoverthrow.exp: check for stap probe in unwinder (timeout)
|
The configuration of this build is:
CI config tcwg_gdb_check master-arm
configure and test flags: --target arm-linux-gnueabihf
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
The configuration of this build is:
CI config tcwg_gdb_check master-arm
configure and test flags: --target arm-linux-gnueabihf
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3278/artifac…
Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1919/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.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
Fixed at r15-4720-ge320846fec00aa
On Mon, 28 Oct 2024 at 01:20, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1390 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-4709-gb281e13ecad1
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Oct 8 21:15:18 2024 +0100
> |
> | libstdc++: Add P1206R7 from_range members to std::vector [PR111055]
> |
> | This is another piece of P1206R7, adding new members to std::vector and
> | std::vector<bool>.
> |
> | ... 40 lines of the commit log omitted.
>
> FAIL: 2 regressions
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++23 (test for excess errors)
> | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++26 (test for excess errors)
> |
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
> configure and test flags: --target arm-linux-gnueabihf
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/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/2927/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/ar…
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
> configure and test flags: --target arm-linux-gnueabihf
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2926/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=b281e13ecad12d07209924a72…
Hi there!
These are legitimate regressions: the code compiled to bogus BIND(C) ABI that only worked when using with Fortran to Fortran. A TODO is now correctly emitted until the proper ABI is implemented.
In Fujitsu-Fortran-0379_0074
```
function strfunc() bind(C)
type,bind(C) :: str
integer :: iii
end type
type(str) :: strfunc
end function
end interface
type,bind(C) :: str
integer :: iii
end type
````
Previously, the result was passed in as a hidden extra argument, like it is done in normal Fortran ABI. On ARM, the equivalent C code is returned in registered as far as I can see: https://godbolt.org/z/nec6jbhYM
0384_0028.f90 also has BIND(C) function returning such BIND(C) types.
So, both tests should not be run on ARM, or should expect a TODO error message until the feature is implemented on ARM.
Jean
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Monday, October 14, 2024 11:23 PM
To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com
Cc: maxim.kuvyrkov(a)linaro.org; Jean Perier <jperier(a)nvidia.com>
Subject: [Linaro-TCWG-CI] llvmorg-20-init-8878-g367c3c968eb8: FAIL: 2 regressions on aarch64
External email: Use caution opening links or attachments
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/LLVM-1398 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld after:
| commit llvmorg-20-init-8878-g367c3c968eb8
| Author: jeanPerier <jperier(a)nvidia.com>
| Date: Mon Oct 14 09:35:29 2024 +0200
|
| [flang] correctly deal with bind(c) derived type result ABI (#111969)
|
| Derived type results of BIND(C) function should be returned according
| the the C ABI for returning the related C struct type.
|
| ... 15 lines of the commit log omitted.
FAIL: 2 regressions
The configuration of this build is:
* 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 : 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=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$WORKSPACE/test/test-suite"
regressions.sum:
| === test-suite tests ===
|
| Running test-suite:Fujitsu/Fortran/0379 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0379/Fujitsu-Fortran-0379_0074.test
|
| Running test-suite:Fujitsu/Fortran/0384 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0384/Fujitsu-Fortran-0384_0028.test
|
| # "NOEXE" means : the test program cannot be compiled
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
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_vls-lto-l…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
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/367c3c968eb8f29b55fb8019b2464c7…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1377 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit v9.1.0-759-g07f0d32641e
| Author: Paolo Bonzini <pbonzini(a)redhat.com>
| Date: Thu Oct 3 16:28:43 2024 +0300
|
| Require meson version 1.5.0
|
| This is needed for Rust support.
|
| Signed-off-by: Paolo Bonzini <pbonzini(a)redhat.com>
| ... 3 lines of the commit log omitted.
The configuration of this build is:
CI config tcwg_gnu_cross_build master-aarch64
configure and test flags: --target aarch64-linux-gnu
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 --:
2
# build_abe linux:
3
# build_abe glibc:
4
# build_abe stage2 --:
5
# build_abe gdb:
6
# build_abe qemu:
7
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/854/ar…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/853/ar…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s…
Full commit : https://gitlab.com/qemu-project/qemu/commit/07f0d32641e04703e6ed9626d061790…
Thanks for the report, I have opened
https://github.com/llvm/llvm-project/issues/111903 for this.
On Tue, Oct 08, 2024 at 07:40:22AM +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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/LLVM-1390 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_kernel/llvm-master-aarch64-lts-allmodconfig after:
>
> | commit llvmorg-20-init-8119-gd2408c417cfa
> | Author: David Green <david.green(a)arm.com>
> | Date: Sun Oct 6 10:44:21 2024 +0100
> |
> | [InstCombine] Canonicalize more geps with constant gep bases and constant offsets. (#110033)
> |
> | This is another small but hopefully not performance negative step to
> | canonicalizing towards i8 geps. We looks for geps with a constant offset
> | base pointer of the form `gep (gep @glob, C1), x, C2` and expand the gep
> | ... 2 lines of the commit log omitted.
>
> The configuration of this build is:
> CI config tcwg_kernel/llvm-master-aarch64-lts-allmodconfig
> Results changed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 24511
>
> From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 33835
> # linux build successful:
> all
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allmodconfig…
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-lts-allmodconfig…
>
> 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/d2408c417cfa71f1786c90978856037…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1372 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit glibc-2.40.9000-232-gd40ac01cbbc
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Thu Oct 3 15:41:10 2024 -0300
|
| stdlib: Make abort/_Exit AS-safe (BZ 26275)
|
| The recursive lock used on abort does not synchronize with a new process
| creation (either by fork-like interfaces or posix_spawn ones), nor it
| is reinitialized after fork().
| ... 60 lines of the commit log omitted.
FAIL: 5 regressions
The configuration of this build is:
CI config tcwg_gnu_native_check_gdb master-aarch64
configure and test flags: --target aarch64-linux-gnu
regressions.sum:
| === gdb tests ===
|
| Running gdb:gdb.reverse/waitpid-reverse.exp ...
| ERROR: GDB process no longer exists
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: check waitpid record
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: continue to breakpoint: marker2
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: reverse to marker1
| UNRESOLVED: gdb.reverse/waitpid-reverse.exp: set breakpoint at marker1
|
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
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_gdb--master-aarch64-build/1…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…
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=d40ac01cbbc66e6d9dbd…
On Thu, 10 Oct 2024 at 06:33, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1370 , please let us know if you are looking at the problem and/or when you have a fix.
I'm not sure what the problem is here. It looks like the build uses
--enable-clocale=gnu and so I would expect the test to PASS on this
target, like it does on x86_64-pc-linux-gnu. Maybe it's a newlib vs
glibc difference. Looking into it ...
>
> In arm-eabi v7-a softfp after:
>
> | commit gcc-15-4016-gc534e37facc
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Sep 24 23:20:56 2024 +0100
> |
> | libstdc++: Populate std::time_get::get's %c format for C locale
> |
> | We were using the empty string "" for D_T_FMT and ERA_D_T_FMT in the C
> | locale, instead of "%a %b %e %T %Y" as the C standard requires. Set it
> | correctly for each locale implementation that defines time_members.cc.
> | ... 18 lines of the commit log omitted.
>
> FAIL: 1 regressions
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
> configure and test flags: --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 22_locale/time_get/get/wchar_t/5.cc -std=gnu++17 execution test
> |
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/c534e37faccf481afa9bc28f0605ca0ec3…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1365 , please let us know if you are looking at the problem and/or when you have a fix.
In glibc_check master-arm after:
| commit glibc-2.40.9000-226-g42c810c2cf3
| Author: Joseph Myers <josmyers(a)redhat.com>
| Date: Mon Oct 7 19:44:25 2024 +0000
|
| Add freopen special-case tests: thread cancellation
|
| Add tests of freopen adding or removing "c" (non-cancelling I/O) from
| the mode string (so completing my planned tests of freopen with
| different features used in the mode strings). Note that it's in the
| ... 5 lines of the commit log omitted.
FAIL: 1 regressions
The configuration of this build is:
CI config tcwg_glibc_check master-arm
configure and test flags: --target arm-linux-gnueabihf
regressions.sum:
| === glibc tests ===
|
| Running glibc:. ...
| FAIL: lint-makefiles
|
You can find the failure logs in *.log.1.xz files in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1896/artifact/…
Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1894/artifact/…
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=42c810c2cf3554afbdd6…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/LLVM-1379 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_flang_build/main-aarch64 after:
| commit llvmorg-20-init-8106-ge36a39346796
| Author: Matthias Springer <me(a)m-sp.org>
| Date: Sat Oct 5 21:46:31 2024 +0200
|
| [mlir][SPIRV] Fix build error (#111264)
|
| Fix build error that was introduced by #111250. Also, the deleted
| function is not needed at all.
|
| ... 9 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
1
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/1063/artifac…
Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/1062/artifac…
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/e36a39346796528f75ff01ef1084b2d…
On Fri, Oct 04, 2024 at 07:05:02AM +0000, ci_notify(a)linaro.org wrote:
...
> | commit v6.11-rc4-291-g16531118ba63
> | Author: Denis Benato <benato.denis96(a)gmail.com>
> | Date: Sat Aug 24 16:11:22 2024 +0200
> |
> | iio: bmi323: peripheral in lowest power state on suspend
> |
> | The bmi323 is mounted on some devices that are powered
> | by an internal battery: help in reducing system overall power drain
> | while the system is in s2idle or the imu driver is not loaded
> | ... 5 lines of the commit log omitted.
This should be fixed with
https://git.kernel.org/jic23/iio/c/506a1ac4c4464a61e4336e135841067dbc040aaa
which is on its way for an -rc release.
Cheers,
Nathan
On Mon, 30 Sept 2024 at 07:22, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1358 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In arm-eabi cortex-m0 soft after:
>
> | commit gcc-15-3575-gc07cf418fdde
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Sep 10 14:25:41 2024 +0100
> |
> | libstdc++: std::string move assignment should not use POCCA trait [PR116641]
> |
> | The changes to implement LWG 2579 (r10-327-gdb33efde17932f) made
> | std::string::assign use the propagate_on_container_copy_assignment
> | (POCCA) trait, for consistency with operator=(const basic_string&).
> | ... 18 lines of the commit log omitted.
>
> FAIL: 2 regressions
>
> regressions.sum:
> | === libstdc++ tests ===
> |
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 (test for excess errors)
> | UNRESOLVED: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 compilation failed to produce executable
> |
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
=== libstdc++ Summary ===
# of expected passes 6036
# of unexpected failures 4689 <<< !!!
Is that normal for this configuration?!
The new testcase fails for the same reason as the 4000 other tests:
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(__deregister_frame_info): Unknown destination type (ARM/Thumb) in
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/./gcc/crtbegin.o
crtstuff.c:(.text+0x5e): dangerous relocation: unsupported relocation
So I don't think this is a problem in the commit, I think it's just a
configuration that isn't well supported.
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
>
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/c07cf418fdde0c192e370a8d76a991cc72…
On 9/23/24 2:08 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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We understand that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In gcc_check master-arm after:
>
> | gcc patch https://patchwork.sourceware.org/patch/97864
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Mon Sep 23 11:06:11 2024 -0400
> |
> | libstdc++: #ifdef out #pragma GCC system_header
> |
> | Tested x86_64-pc-linux-gnu, OK for trunk?
> |
> | -- 8< --
> |
> | In r15-3714-gd3a7302ec5985a I added -Wsystem-headers to the libstdc++ build
> | ... 379 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 4700ad1c78c c++: diagnose this specifier in requires expr [PR116798]
>
> FAIL: 3 regressions
>
> regressions.sum:
> === libstdc++ tests ===
>
> Running libstdc++:libstdc++-dg/conformance.exp ...
> FAIL: 17_intro/headers/c++2011/parallel_mode.cc (test for excess errors)
> FAIL: 17_intro/headers/c++2014/parallel_mode.cc (test for excess errors)
> FAIL: 17_intro/headers/c++2017/parallel_mode.cc -std=gnu++17 (test for excess errors)
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/9301/artifac…
> 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/9301/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/9301/artifac…
Thanks, I believe
https://gcc.gnu.org/pipermail/gcc-patches/2024-September/663711.html
should fix this.