On 2025-11-04 12:03, ci_notify@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-16-5025-g0013501e462 | Author: Siddhesh Poyarekar siddhesh@gotplt.org | Date: Mon Nov 3 17:02:00 2025 -0600 | | lto/122515: Fix archive offset types for i686 | | On i686, offsets into object archives could be 64-bit, but they're | inconsistently treated across the lto, which may sometimes result in | truncation of those offsets for large archives. | ... 36 lines of the commit log omitted.
Produces 3 regressions: | | regressions.sum: | Running gcc:gcc.dg/lto/lto.exp ... | UNRESOLVED: gcc.dg/lto/pr122515 c_lto_pr122515_0.o-c_lto_pr122515.a execute -flto=auto -ffat-lto-objects | UNRESOLVED: gcc.dg/lto/pr122515 c_lto_pr122515_0.o-c_lto_pr122515.a link -flto=auto -ffat-lto-objects | FAIL: gcc.dg/lto/pr122515, ar returned 1: /WORKSPACE/abe/builds/destdir/aarch64-unknown-linux-gnu/bin/gcc-ar: Cannot find plugin 'liblto_plugin.so'
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-1744. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain@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
The full lists of regressions and improvements as well as configure and make commands are in
The Jenkins instance seems to be down. Is there another way to find out how this was configured? ISTM that liblto_plugin.so may not have been built.
Sid
linaro-toolchain@lists.linaro.org
-
Siddhesh Poyarekar