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.