Regressions on master at commit r16-1494 vs commit r16-1490 on Linux/x86_64
Regressions on master at commit r16-1494 vs commit r16-1490 on Linux/x86_64 New failures: FAIL: 30_threads/async/async.cc -std=gnu++17 execution test New passes:
Regressions on native/master at commit r16-1490 vs commit r16-1485 on Linux/x86_64
Regressions on master at commit r16-1490 vs commit r16-1485 on Linux/x86_64 New failures: FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-3_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-3_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-tr1_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-tr1_b.C -std=c++26 (test for excess errors) New passes:
Regressions on master at commit r16-1488 vs commit r16-1485 on Linux/x86_64
Regressions on master at commit r16-1488 vs commit r16-1485 on Linux/x86_64 New failures: FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-3_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-3_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-header_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-tr1_b.C -std=c++26 (test for excess errors) FAIL: g++.dg/modules/xtreme-tr1_b.C -std=c++26 (test for excess errors) New passes:
[Linaro-TCWG-CI] gcc-16-1487-g774ae8734f0e: 8 regressions on aarch64
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-1487-g774ae8734f0e
| Author: Giuseppe D'Angelo
| Date: Mon Jun 9 23:13:21 2025 +0200
|
| libstdc++: add range support to std::optional (P3168)
|
| This commit implements P3168 ("Give std::optional Range Support"), added
| for C++26. Both begin() and end() are straightforward, implemented using
| normal_iterator over a raw pointer.
| ... 24 lines of the commit log omitted.
Produces 8 regressions:
|
| regressions.sum:
| Running g++:g++.dg/modules/modules.exp ...
| FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors)
| FAIL: g++.dg/modules/xtreme-header-3_b.C -std=c++26 (test for excess errors)
| FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++26 (test for excess errors)
| FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors)
| ... and 4 more
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-1603.
Please let us know if you have a fix.
If you have any questions regarding this report, please ask on
linaro-toolch...@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
*
https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3846/artifact/artifacts/00-sumfiles/
The full lists of regressions and improvements as well as configure and make
commands are in
*
https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3846/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
*
https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3846/artifact/artifacts/sumfiles/xfails.xfail
Current build :
https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3846/artifact/artifacts
Reference build :
https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3845/artifact/artifacts
Instruction to reproduce the build :
https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1/774ae8734f0e199a8c6d29dd8c186b893385470b/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt
Full commit : See in git+ssh://linar...@gcc.gnu.org/git/gcc.git
RE: [r16-1429 Regression] FAIL: g++.target/i386/vect-pragma-target-2.C -std=gnu++98 (test for excess errors) on Linux/x86_64
I will do that.
Thx,
Haochen
From: Andrew Pinski
Sent: Thursday, June 12, 2025 10:52 PM
Cc: gb.de...@gmail.com; gcc-regression@gcc.gnu.org; GCC Patches
; Jiang, Haochen
Subject: Re: [r16-1429 Regression] FAIL: g++.target/i386/vect-pragma-target-2.C
-std=gnu++98 (test for excess errors) on Linux/x86_64
On Wed, Jun 11, 2025, 10:17 PM haochen.jiang
mailto:haoch...@smtp.intel.com>> wrote:
On Linux/x86_64,
dcb9af06212e8bb36e84a1b8498c625c29abeb6f is the first bad commit
commit dcb9af06212e8bb36e84a1b8498c625c29abeb6f
Author: Gwenole Beauchesne mailto:gb.de...@gmail.com>>
Date: Mon Jun 2 14:44:55 2025 -0700
c/c++: Handle '#pragma GCC target optimize' early [PR48026]
caused
FAIL: gcc.target/i386/vect-pragma-target-1.c scan-assembler-times
vpaddw.+zmm[0-9]+ 1
FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++17
scan-assembler-times vpaddw.+zmm[0-9]+ 1
FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++26
scan-assembler-times vpaddw.+zmm[0-9]+ 1
FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++98
scan-assembler-times vpaddw.+zmm[0-9]+ 1
Can someone file a bug for this. It is just a testcase issue so I am willing to
let it broken until I get back from vacation.
with GCC configured with
../../gcc/configure
--prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-1429/usr
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl
--enable-libmpx x86_64-linux --disable-bootstrap
To reproduce:
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-pragma-target-1.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-pragma-target-1.c
--target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-1.C
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-1.C
--target_board='unix{-m64\ -march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
Re: [r16-1429 Regression] FAIL: g++.target/i386/vect-pragma-target-2.C -std=gnu++98 (test for excess errors) on Linux/x86_64
On Wed, Jun 11, 2025, 10:17 PM haochen.jiang
wrote:
> On Linux/x86_64,
>
> dcb9af06212e8bb36e84a1b8498c625c29abeb6f is the first bad commit
> commit dcb9af06212e8bb36e84a1b8498c625c29abeb6f
> Author: Gwenole Beauchesne
> Date: Mon Jun 2 14:44:55 2025 -0700
>
> c/c++: Handle '#pragma GCC target optimize' early [PR48026]
>
> caused
>
> FAIL: gcc.target/i386/vect-pragma-target-1.c scan-assembler-times
> vpaddw.+zmm[0-9]+ 1
> FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++17
> scan-assembler-times vpaddw.+zmm[0-9]+ 1
> FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++26
> scan-assembler-times vpaddw.+zmm[0-9]+ 1
> FAIL: g++.target/i386/vect-pragma-target-1.C -std=gnu++98
> scan-assembler-times vpaddw.+zmm[0-9]+ 1
>
Can someone file a bug for this. It is just a testcase issue so I am
willing to let it broken until I get back from vacation.
> with GCC configured with
>
> ../../gcc/configure
> --prefix=/export/users3/haochenj/src/gcc-bisect/master/master/r16-1429/usr
> --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
> --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet
> --without-isl --enable-libmpx x86_64-linux --disable-bootstrap
>
> To reproduce:
>
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-pragma-target-1.c
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=gcc.target/i386/vect-pragma-target-1.c
> --target_board='unix{-m64\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-1.C
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="i386.exp=g++.target/i386/vect-pragma-target-1.C
> --target_board='unix{-m64\ -march=cascadelake}'"
>
> (Please do not reply to this email, for question about this report,
> contact me at haochen dot jiang at intel.com)
> (If you met problems with cascadelake related, disabling AVX512F in
> command line might save that.)
> (However, please make sure that there is no potential problems with
> AVX512.)
>
