Re: [r16-22 Regression] FAIL: gcc.dg/pr78408-3.c scan-tree-dump-times forwprop1 "after previous" 1 on Linux/x86_64

On Fri, Apr 18, 2025, 7:29 PM haochen.jiang wrote: > On Linux/x86_64, > > 94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1 is the first bad commit > commit 94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1 > Author: Andrew Pinski > Date: Thu Feb 20 16:09:05 2025 -0800 > > gimple-fold: Improve optimize_memc

[r16-22 Regression] FAIL: gcc.dg/pr78408-3.c scan-tree-dump-times forwprop1 "after previous" 1 on Linux/x86_64

On Linux/x86_64, 94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1 is the first bad commit commit 94f275432f7ea4781ec7c05fa9d1d81ef6cb3fc1 Author: Andrew Pinski Date: Thu Feb 20 16:09:05 2025 -0800 gimple-fold: Improve optimize_memcpy_to_memset to handle STRING_CST [PR78408] caused FAIL: gcc.dg/

[r16-23 Regression] FAIL: gcc.dg/pr118947-1.c scan-tree-dump-times forwprop1 "after previous" 1 on Linux/x86_64

On Linux/x86_64, 7b4849ec79873fa6de98436deda47e19cbac32ef is the first bad commit commit 7b4849ec79873fa6de98436deda47e19cbac32ef Author: Andrew Pinski Date: Mon Feb 24 12:33:32 2025 -0800 gimple-fold: Improve optimize_memcpy_to_memset by walking back until aliasing says the ref is a may

RE: Regressions on native/master at commit r16-29 vs commit r16-21 on Linux/x86_64

I have a fix for the testcases. Just need to increase the size from 32 to 1024. Basically with 32, vectors are used for the memcpy which allows to optimize it; just differently and not what is being tested here. I am hoping 1024 is big enough not to hit another target which does memcpy for 1024

Re: Regressions on native/master at commit r16-29 vs commit r16-21 on Linux/x86_64

This builder uses --with-arch=native. The (a) difference starts at x86-64-v3: $ diff -u <(gcc -O2 -fdump-tree-forwprop1-details=- -O2 gcc.dg/pr78408-3.c -c -march=x86-64-v2) <(gcc -O2 -fdump-tree-forwprop1-details=- -O2 gcc.dg/pr78408-3.c -c -march=x86-64-v3) --- /dev/fd/63 2025-04-19 01:27:31

Regressions on native/master at commit r16-29 vs commit r16-21 on Linux/x86_64

Regressions on master at commit r16-29 vs commit r16-21 on Linux/x86_64 New failures: FAIL: gcc.dg/pr118947-1.c scan-tree-dump-times forwprop1 "after previous" 1 FAIL: gcc.dg/pr118947-1.c scan-tree-dump-times forwprop1 "after previous" 1 FAIL: gcc.dg/pr78408-3.c scan-tree-dump-times forwprop1 "afte

Regressions on releases/gcc-14 at commit r14-11649 vs commit r14-11648 on Linux/x86_64

Regressions on releases/gcc-14 at commit r14-11649 vs commit r14-11648 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:

[Linaro-TCWG-CI] gcc-15-9463-gaa3e72f9430: 2 regressions on arm

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In bootstrap_check master-arm-check_bootstrap, after: | commit gcc-15-9463-gaa3e72f9430 | Author: Thomas Schwinge | Date: Thu Mar 27 23:06:37 2025 +0100 | | Add t

Regressions on master at commit r15-9539 vs commit r15-9536 on Linux/x86_64

Regressions on master at commit r15-9539 vs commit r15-9536 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

releases/gcc-13 branch: commit r13-9549 failed to bootstrap on Linux/x86_64 (commit r13-9546 builds)!

RUNTESTFLAGS=--target_board=unix{-m32,} ../src-13/configure --with-arch=corei7 --with-cpu=corei7 --enable-clocale=gnu --with-system-zlib --enable-shared --enable-cet --with-demangler-in-ld --enable-libmpx --prefix=/usr/gcc-13.3.1 --with-fpmath=sse