Hi,
thanks for the report. I looked into this and I dont think my patch is
actually responsible for these failures. The gcov-39.c prime-paths test
seems to be a pre-existing flaky test rather than something introduced by
my changes — my patch only touches the tree optimization path (final value
replacement logic) and has no interaction with gcov instrumentation or path
coverage counting.
Could someone check if this failure shows up in the baseline as well?
Happy to dig deeper if needed, but from what I can see this looks unrelated
to my patch.
Thanks
---------
Lunex<imlunex2011(a)gmail.com>
> From: ci_notify(a)linaro.org
> Date: Thu, 27 Aug 2026 14:30:00 +0000 (UTC)
> Reply-To: linaro-toolchain(a)lists.linaro.org
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
My manual investigation process has detected a problem with that
conclusion, and ditto.
> In aarch64 native, after:
> | gcc patch https://patchwork.sourceware.org/patch/142242
> | Author: Hans-Peter Nilsson <hp(a)axis.com>
> | Date: Wed Aug 26 15:16:16 2026 +0200
> |
> | NOT vs. ROTATE (was: [CRIS PATCH] Support bitreverse32, rotatesi3_16 and other swap variants.)
> |
> | > From: Hans-Peter Nilsson <hp(a)axis.com>
> | > Date: Tue, 25 Aug 2026 17:50:01 +0200
> |
> | ... 36 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | d9dcc189896 fortran: array descriptor: Move dtype layout constants out of header [PR122521]
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
That's quite unlikely, as that message was a suggestion for a
documentation patch that touched only gcc/doc/md.texi.
I have a hunch gcc.misc-tests/gcov-39.c is flaky, if not generally
then at least in the context of your CI. I suggest you consider
filtering out that test until your human resources has investigated
the flakiness.
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
brgds, H-P
Hi,
I believe these may be flaky since I checked with my 4 patches on
cfarm185 machine with following configure command
configure --prefix=/home/avinashd/opt --enable-languages=c,c++ --
target=aarch64-unknown-linux-gnu --disable-multilib --enable-fix-
cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --
disable-bootstrap
on top of the commit
a5da203dd95900ba8bab16432667989f3d018c76 : xtensa: Make use of CONST.S
instruction
On Fri, 2026-08-28 at 22:17 +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 aarch64 native, after:
> | 4 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/142333
> | 25ff335aad8 [PATCH 4/4] rs6000: Add sha3 builtins and
> documentation [RFC02645]
> | f47d33c1b4e [PATCH 3/4] rs6000: Add __dmr2048 type (QDOmode) and
> map it to DMR pair register
> | 1eb45af654c [PATCH 2/4] genmodes: Use wider types for
> mode_unit_size array based on max size
The only change in middle-end that has happened is with this patch
(2/4). And that is to generate the macro MODE_UNIT_SIZE_TYPE instead of
unsigned char. This should not have caused the below mentioned
regressions. All other patches are rs6000 backend related.
Please let me know if these regressions are always reproducible or if I
have tested it incorrectly on the cfarm185 machine. I can have a look
at what is happening.
Thanks,
Avinash Jayakar
> | 63b651a8d8f [PATCH 1/4] rs6000: Add sha2 and shapad builtins
> [RFC02645]
> | ... applied on top of baseline commit:
> | aaa0f6b1e87 match.pd: fold reductions of vector duplicates and
> repeats [PR127039]
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0
> in branch percentages, 0 in condition/decision, 1 in prime-paths, 0
> in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered
> paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-
> linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-
> fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<----------------------
> ----8<--------------------------
>
> The information below contains the details of the failures, and the
> ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure
> and make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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,
My changes are PowerPC specific, I don't understand how aarch64 failures
are due to my changes.
| FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
| FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
Should I wait for another build? or try to reproduce this issue on cfram
machine (Aarch64) ?
Thanks,
Manjunath S Matti.
On 24/08/26 6:05 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 aarch64 native, after:
> | gcc patch https://patchwork.sourceware.org/patch/142026
> | Author: Manjunath S Matti <mmatti(a)linux.ibm.com>
> | Date: Sun Aug 23 10:57:59 2026 -0500
> |
> | [PATCH] rs6000: Fix ICE with __int128 vector built-ins and -mno-vsx [PR126512]
> |
> | The changes have been bootstrapped and regression tested on
> | powerpc64le-linux and powerpc64-linux.
> |
> | ... 29 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 1ccae7a1e12 AVR: target/127024 - Fix build warning: skipping two-word instruction
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
No, this isn't plausible. The maintainer_utils changes have no effect at all on the compiler. So there must be some other cause.
R.
On 21/08/2026 15:45, 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 aarch64 native, after:
> | 5 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/141841
> | 237059276db [PATCH v1 5/5] maintainer_utils: more array size verification.
> | 4891de9f00a [PATCH v1 4/5] maintainer_utils: Ensure the list of user data is sorted.
> | f18b6593669 [PATCH v1 3/5] maintainer_utils: Move DCO entries outside of roles.
> | 3126c9b698f [PATCH v1 2/5] maintainer_utils: Fix errors in schema.
> | 9145fb8e995 [PATCH v1 1/5] maintainer_utils.py: Add a store method
> | ... applied on top of baseline commit:
> | de8bbe99481 Add fixme comment to vect_slp_node_weight and containing_loop
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
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,
Two independent failures were observed in the test-suite.
Both failures are caused by pre-existing undefined behavior in the test programs:
1. Accessing elements through a std::initializer_list after the lifetime of its backing temporary array has ended.
2. Reading uninitialized automatic variables.
The commit (efd053f) merely exposed these latent issues through improved lifetime-aware optimization.
Therefore, this is the test-suite issue, not a compiler defect.
Please ignore the mail. We will update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信日時: 2026年8月21日 21:40
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: isoard(a)amd.com <isoard(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-4794-gefd053f8ef30: 3 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-24-init-4794-gefd053f8ef30
| Author: Alexandre Isoard <isoard(a)amd.com>
| Date: Tue Aug 18 07:36:19 2026 -0700
|
| [PromoteMemToReg] Insert store undef when removing lifetime markers (#191909)
|
| The `lifetime.start` and `lifetime.end` can help avoid the creation of
| spurious phi-node.
|
| ... 20 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C++/0041 ...
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0335.test
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0337.test
| Running test-suite:Fujitsu/C/0096 ...
| FAIL: test-suite :: Fujitsu/C/0096/Fujitsu-C-0096_0358.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2266. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/efd053f8ef306e6fa21ab0cd1bd185e…
Thanks for the report. I compared builds 10158 and 10159.
The additional breakpoint is for _dl_relocate_static_pie_ifunc in
static-reloc.c:28. Before b6477e6c4ef, the function and its symbol were
already present, but its IPA-ICF wrapper had no address-bearing subprogram
DIE. With the change, GDB can now see the function when minsyms=False and
set a breakpoint on it.
This is the behavior PR debug/126355 was intended to restore, so the result
also provides useful confirmation that the GCC fix is effective.
The failure comes from py-rbreak.exp using the unanchored regexp "func.*".
It now also matches the "ifunc" suffix of _dl_relocate_static_pie_ifunc,
changing the result from nine breakpoints to ten. GDB, glibc, binutils and
Linux are unchanged between the two builds; the GCC revisions are this
commit and its immediate parent.
Changing the expected count to ten would make the test depend on the target
startup objects. A more robust fix would be to narrow the two unscoped
regexp uses in the exact-count and throttle checks, for example to
"^e?func.*", so that they only select functions defined by the test.
I therefore do not think this is a GCC regression. It looks like the GDB
test needs to be made more specific.
<ci_notify(a)linaro.org> 于2026年8月24日周一 11:47写道:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In aarch64 native, after:
> | commit gcc-17-3278-gb6477e6c4ef
> | Author: Longjun Luo <luolongjuna(a)gmail.com>
> | Date: Thu Jul 23 00:01:50 2026 +0800
> |
> | debug/126355 - preserve debug info for IPA ICF wrappers
> |
> | When IPA ICF keeps a distinct symbol for an address-taken function
> by
> | replacing its body with a wrapper, cgraph_node::create_wrapper
> reuses the
> | original function declaration and its early debug DIE.
> | ... 28 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running gdb:gdb.python/py-rbreak.exp ...
> | FAIL: gdb.python/py-rbreak.exp: check number of returned breakpoints
> is 9
>
> Used configuration :
> *CI config* tcwg_gnu_native_check_gdb aarch64-linux-gnu
> *configure and test flags:* none, autodetected on
> aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769
> --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-2005. (Require Linaro login)
> Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
>
> Instruction to reproduce the build :
> https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-arm_eabi, after:
| commit v11.1.0-302-g288d39e26d4
| Author: Richard Henderson <richard.henderson(a)linaro.org>
| Date: Mon Aug 10 09:08:31 2026 -0700
|
| tcg: Simplify bswap/hswap expansion using bitswap
|
| Reviewed-by: Philippe Mathieu-Daudé <philmd(a)oss.qualcomm.com>
| Signed-off-by: Richard Henderson <richard.henderson(a)linaro.org>
Produces 14 regressions:
|
| regressions.sum:
| Running gcc:gcc.target/aarch64/advsimd-intrinsics/advsimd-intrinsics.exp ...
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O0 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O1 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O2 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
| ... and 11 more
Used configuration :
*CI config* tcwg_gnu_embed_check_gcc master-arm_eabi
*configure and test flags:* --target arm-eabi
We track this bug report under https://linaro.atlassian.net/browse/GNU-2006. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/…
Full commit : https://gitlab.com/qemu-project/qemu/commit/288d39e26d48ed26e4f786ddb3a25ee…