Regressions on native/master at commit r15-2217 vs commit r15-2210 on Linux/x86_64
Regressions on master at commit r15-2217 vs commit r15-2210 on Linux/x86_64 New failures: FAIL: libgomp.c++/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-3.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-5.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-6.c execution test New passes: FAIL: c-c++-common/dfp/convert-bfp-10.c execution test FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++14 execution test FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++17 execution test FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++20 execution test FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++98 execution test FAIL: c-c++-common/dfp/convert-bfp-2.c execution test FAIL: c-c++-common/dfp/convert-bfp-2.c -std=c++14 execution test FAIL: c-c++-common/dfp/convert-bfp-2.c -std=c++17 execution test FAIL: c-c++-common/dfp/convert-bfp-2.c -std=c++20 execution test FAIL: c-c++-common/dfp/convert-bfp-2.c -std=c++98 execution test FAIL: c-c++-common/dfp/convert-bfp-6.c execution test FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++14 execution test FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++17 execution test FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++20 execution test FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test FAIL: c-c++-common/dfp/convert-bfp.c execution test FAIL: c-c++-common/dfp/convert-bfp.c -std=c++14 execution test FAIL: c-c++-common/dfp/convert-bfp.c -std=c++17 execution test FAIL: c-c++-common/dfp/convert-bfp.c -std=c++20 execution test FAIL: c-c++-common/dfp/convert-bfp.c -std=c++98 execution test
[r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test on Linux/x86_64
On Linux/x86_64,
88d16194d0c8a6bdc2896c8944bfbf3e6038c9d2 is the first bad commit
commit 88d16194d0c8a6bdc2896c8944bfbf3e6038c9d2
Author: Jeff Law
Date: Mon Jul 22 08:45:10 2024 -0600
[NFC][PR rtl-optimization/115877] Avoid setting irrelevant bit groups as
live in ext-dce
caused
FAIL: c-c++-common/dfp/convert-bfp-10.c execution test
FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++14 execution test
FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++17 execution test
FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++20 execution test
FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++98 execution test
FAIL: c-c++-common/dfp/convert-bfp-6.c execution test
FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++14 execution test
FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++17 execution test
FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++20 execution test
FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-2196/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="dfp.exp=c-c++-common/dfp/convert-bfp-10.c
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dfp.exp=c-c++-common/dfp/convert-bfp-10.c
--target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dfp.exp=c-c++-common/dfp/convert-bfp-6.c
--target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dfp.exp=c-c++-common/dfp/convert-bfp-6.c
--target_board='unix{-m32\ -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.)
Regressions on native/master at commit r15-2226 vs commit r15-2217 on Linux/x86_64
Regressions on master at commit r15-2226 vs commit r15-2217 on Linux/x86_64 New failures: New passes: FAIL: libgomp.c++/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-11.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-3.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-5.c execution test FAIL: libgomp.c/../libgomp.c-c++-common/for-6.c execution test
Regressions on master at commit r15-2234 vs commit r15-2230 on Linux/x86_64
Regressions on master at commit r15-2234 vs commit r15-2230 on Linux/x86_64 New failures: FAIL: c-c++-common/musttail12.c -std=c++14 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++17 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++20 (test for excess errors) FAIL: g++.dg/musttail6.C (test for excess errors) New passes:
Regressions on master at commit r15-2234 vs commit r15-2230 on Linux/i686
Regressions on master at commit r15-2234 vs commit r15-2230 on Linux/i686 New failures: FAIL: c-c++-common/musttail12.c -std=c++14 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++17 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++20 (test for excess errors) FAIL: g++.dg/musttail6.C (test for excess errors) New passes:
Regressions on native/master at commit r15-2234 vs commit r15-2230 on Linux/x86_64
Regressions on master at commit r15-2234 vs commit r15-2230 on Linux/x86_64 New failures: FAIL: c-c++-common/musttail12.c -std=c++14 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++17 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++20 (test for excess errors) FAIL: g++.dg/musttail6.C (test for excess errors) New passes:
RE: [r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test on Linux/x86_64
It might be a false positive timeout alert. Please ignore that first.
Thx,
Haochen
> -Original Message-
> From: haochen.jiang
> Sent: Tuesday, July 23, 2024 7:51 PM
> To: j...@ventanamicro.com; gcc-regression@gcc.gnu.org; gcc-
> patc...@gcc.gnu.org; Jiang, Haochen
> Subject: [r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c -
> std=gnu++98 execution test on Linux/x86_64
>
> On Linux/x86_64,
>
> 88d16194d0c8a6bdc2896c8944bfbf3e6038c9d2 is the first bad commit
> commit 88d16194d0c8a6bdc2896c8944bfbf3e6038c9d2
> Author: Jeff Law
> Date: Mon Jul 22 08:45:10 2024 -0600
>
> [NFC][PR rtl-optimization/115877] Avoid setting irrelevant bit groups as
> live
> in ext-dce
>
> caused
>
> FAIL: c-c++-common/dfp/convert-bfp-10.c execution test
> FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++14 execution test
> FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++17 execution test
> FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++20 execution test
> FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++98 execution test
> FAIL: c-c++-common/dfp/convert-bfp-6.c execution test
> FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++14 execution test
> FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++17 execution test
> FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++20 execution test
> FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-
> bisect/master/master/r15-2196/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="dfp.exp=c-c++-
> common/dfp/convert-bfp-10.c --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dfp.exp=c-c++-
> common/dfp/convert-bfp-10.c --target_board='unix{-m32\ -
> march=cascadelake}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dfp.exp=c-c++-
> common/dfp/convert-bfp-6.c --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dfp.exp=c-c++-
> common/dfp/convert-bfp-6.c --target_board='unix{-m32\ -
> 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: [r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test on Linux/x86_64
On 7/23/24 7:49 PM, Jiang, Haochen wrote: It might be a false positive timeout alert. Please ignore that first. Funny, I was wondering about that -- I couldn't get them to fail. Jeff
Re: [r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test on Linux/x86_64
On Wed, Jul 24, 2024 at 01:49:06AM +, Jiang, Haochen wrote: > It might be a false positive timeout alert. Please ignore that first. It is not. I'm seeing it too consistently on i686-linux: obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++11 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++14 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++17 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++20 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++23 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++26 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++98 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++11 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++14 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++17 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++20 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++23 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++26 execution test obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++11 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++14 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++17 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++20 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++23 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++26 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++98 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++11 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++14 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++17 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++20 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++23 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++26 execution test obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test The compilation of convert-bfp-6.c itself is identical between the older (where it didn't fail) and newer (where it fails) builds, what has changed is libgcc.a. In particular, what matters is libgcc/bid_binarydecimal.o. If I link all objects from libgcc from older (good libgcc) but bid_binarydecimal.o (that one from newer bad libgcc), convert-bfp-6 still aborts, if I link all objects from libgcc from newer (bad libgcc) but bid_binarydecimal.o (that one from older good libgcc), convert-bfp-6 works. Jakub
RE: [r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 execution test on Linux/x86_64
> -Original Message- > From: Jakub Jelinek > Sent: Wednesday, July 24, 2024 1:09 PM > To: Jiang, Haochen > Cc: j...@ventanamicro.com; gcc-regression@gcc.gnu.org; gcc- > patc...@gcc.gnu.org > Subject: Re: [r15-2196 Regression] FAIL: c-c++-common/dfp/convert-bfp-6.c > -std=gnu++98 execution test on Linux/x86_64 > > On Wed, Jul 24, 2024 at 01:49:06AM +, Jiang, Haochen wrote: > > It might be a false positive timeout alert. Please ignore that first. > > It is not. I'm seeing it too consistently on i686-linux: > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++11 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++14 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++17 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++20 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++23 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++26 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++98 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++11 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++14 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++17 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++20 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++23 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++26 > execution test > obj49/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++11 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++14 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++17 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++20 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++23 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++26 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-10.c -std=c++98 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++11 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++14 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++17 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++20 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++23 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++26 > execution test > obj51/LOGT:FAIL: c-c++-common/dfp/convert-bfp-6.c -std=gnu++98 > execution test > > The compilation of convert-bfp-6.c itself is identical between the older > (where > it didn't fail) and newer (where it fails) builds, what has changed is > libgcc.a. > In particular, what matters is libgcc/bid_binarydecimal.o. > If I link all objects from libgcc from older (good libgcc) but > bid_binarydecimal.o > (that one from newer bad libgcc), convert-bfp-6 still aborts, if I link all > objects > from libgcc from newer (bad libgcc) but bid_binarydecimal.o (that one from > older good libgcc), convert-bfp-6 works. I see. If it is not a false alarm, then it seems to me that gcc-15-2212-gad642d2c950 from Jeff might fix the problem from the regression report. But I am not sure if it really fix the problem or happen to be right. Thx, Haochen > > Jakub
