master branch: commit r15-1643 failed to bootstrap on Linux/i686 (commit r15-1594 builds)!

make[2]: Entering directory '/home/haochenj/src/gcc-regression' rm -rf bld mkdir -p bld cd bld; \ CC="gcc -m32 -fno-lto" CXX="g++ -m32 -fno-lto" ../src-master/configure \ --with-arch=corei7 --with-cpu=intel --enable-clocale=gnu --with-system-zlib --enable-shared --enable-cet --with-demangl

master branch: commit r15-1643 failed to bootstrap on Linux/x86_64 (commit r15-1594 builds)!

make[2]: Entering directory '/export/home/haochenj/src/gcc-regression' rm -rf bld mkdir -p bld cd bld; \ RUNTESTFLAGS="--target_board='unix{-m32,}'" ../src-master/configure \ --with-arch=corei7 --with-cpu=corei7 --enable-clocale=gnu --with-system-zlib --enable-shared --enable-cet --with-de

Regressions on master at commit r15-1646 vs commit r15-1594 on Linux/i686

Regressions on master at commit r15-1646 vs commit r15-1594 on Linux/i686 New failures: FAIL: gcc.dg/dfp/bitint-4.c execution test FAIL: gcc.target/i386/pr63527.c scan-assembler-not movl[ \t]%[^,]+, %ebx FAIL: gcc.target/i386/pr91384.c scan-assembler-not testl New passes:

Regressions on master at commit r15-1647 vs commit r15-1594 on Linux/x86_64

Regressions on master at commit r15-1647 vs commit r15-1594 on Linux/x86_64 New failures: FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping" FAIL: gcc.target/i386/force-indirect-call-2.c scan-assembler-times (?:call|jmp)[ \\t]+\\*% 3 FAIL: gcc.target/i386/pr63527.c

Regressions on native/master at commit r15-1646 vs commit r15-1594 on Linux/x86_64

Regressions on master at commit r15-1646 vs commit r15-1594 on Linux/x86_64 New failures: FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping" FAIL: gcc.target/i386/force-indirect-call-2.c scan-assembler-times (?:call|jmp)[ \\t]+\\*% 3 FAIL: gcc.target/i386/pr63527.c

[r15-1619 Regression] FAIL: gcc.target/i386/stack-check-17.c scan-assembler-not pop on Linux/x86_64

On Linux/x86_64, 3b9b8d6cfdf59337f4b7ce10ce92a98044b2657b is the first bad commit commit 3b9b8d6cfdf59337f4b7ce10ce92a98044b2657b Author: Surya Kumari Jangala Date: Tue Jun 25 08:37:49 2024 -0500 ira: Scale save/restore costs of callee save registers with block frequency caused FAIL: gcc

[Linaro-TCWG-CI] gcc-15-1648-gad20ad7dddcb: 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-toolch...@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on

Regressions on master at commit r15-1666 vs commit r15-1662 on Linux/x86_64

Regressions on master at commit r15-1666 vs commit r15-1662 on Linux/x86_64 New failures: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps New passes:

Regressions on master at commit r15-1667 vs commit r15-1666 on Linux/x86_64

Regressions on master at commit r15-1667 vs commit r15-1666 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps

[Linaro-TCWG-CI] gcc-15-1649-g19f630e6ae8d: FAIL: 2 regressions on aarch64

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-toolch...@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on

Re: [PATCH 1/3] Release structures on function return

I think we need to revert this. I got this email from linaro/gcc-regressions: [Linaro-TCWG-CI] gcc-15-1649-g19f630e6ae8d: FAIL: 2 regressions on aarch64 regressions.sum: === gcc tests === Running gcc:gcc.misc-tests/gcov.exp ... FAIL: gcc.misc-tests/gcov-23.c (internal compiler

Re: [Linaro-TCWG-CI] gcc-15-1619-g3b9b8d6cfdf5: FAIL: 4 regressions on aarch64

Hi, I am looking into these regressions. Regards, Surya On 26/06/24 7:51 am, ci_not...@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-toolch...@li