RE: gcc-regression script build fail info

2024-08-12 Thread Jiang, Haochen via Gcc-regression
Ping for this thread. Any ideas? If no, I will change the generated info with command following if we take r15-1643 as example and see if it is clearer: head -26 makelog.r15-1643.x86_64.native | tail -7 > 1.log; grep -E "(error:|Error)" makelog.r15-1643.x86_64.native >> 1.log; echo "=

Regressions on native/master at commit r15-2894 vs commit r15-2893 on Linux/x86_64

2024-08-12 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r15-2894 vs commit r15-2893 on Linux/x86_64 New failures: New passes: FAIL: gfortran.dg/sizeof_6.f90 -O1 execution test

Regressions on native/master at commit r15-2893 vs commit r15-2887 on Linux/x86_64

2024-08-12 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r15-2893 vs commit r15-2887 on Linux/x86_64 New failures: FAIL: gfortran.dg/sizeof_6.f90 -O1 execution test New passes:

Regressions on master at commit r15-2887 vs commit r15-2882 on Linux/x86_64

2024-08-12 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r15-2887 vs commit r15-2882 on Linux/x86_64 New failures: New passes: FAIL: 30_threads/async/async.cc -std=gnu++17 execution test

Regressions on master at commit r15-2882 vs commit r15-2881 on Linux/x86_64

2024-08-12 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r15-2882 vs commit r15-2881 on Linux/x86_64 New failures: FAIL: 30_threads/async/async.cc -std=gnu++17 execution test New passes:

Regressions on master at commit r15-2880 vs commit r15-2876 on Linux/x86_64

2024-08-12 Thread Haochen Jiang via Gcc-regression
Regressions on master at commit r15-2880 vs commit r15-2876 on Linux/x86_64 New failures: New passes: FAIL: gcc.c-torture/execute/pr57344-4.c -O2 -flto -fno-use-linker-plugin -flto-partition=none (internal compiler error: in convert_insn, at config/i386/i386-features.cc:1502) FAIL: gcc.c-tort