On Linux/x86_64,
251ea6dfbdb4448875e41081682bb3aa451b5729 is the first bad commit
commit 251ea6dfbdb4448875e41081682bb3aa451b5729
Author: Roger Sayle <ro...@nextmovesoftware.com>
Date: Fri Mar 11 17:57:12 2022 +0000
PR tree-optimization/98335: New peephole2 xorl;movb -> movzbl
caused
FAIL: libitm.c/memcpy-1.c (internal compiler error: in extract_insn, at
recog.cc:2769)
FAIL: libitm.c/memcpy-1.c (test for excess errors)
FAIL: libitm.c/memset-1.c (internal compiler error: in extract_insn, at
recog.cc:2769)
FAIL: libitm.c/memset-1.c (test for excess errors)
with GCC configured with
../../gcc/configure
--prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-7616/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}/x86_64-linux/libitm/testsuite && make check
RUNTESTFLAGS="c.exp=libitm.c/memcpy-1.c --target_board='unix{-m32}'"
$ cd {build_dir}/x86_64-linux/libitm/testsuite && make check
RUNTESTFLAGS="c.exp=libitm.c/memcpy-1.c --target_board='unix{-m32\
-march=cascadelake}'"
$ cd {build_dir}/x86_64-linux/libitm/testsuite && make check
RUNTESTFLAGS="c.exp=libitm.c/memset-1.c --target_board='unix{-m32}'"
$ cd {build_dir}/x86_64-linux/libitm/testsuite && make check
RUNTESTFLAGS="c.exp=libitm.c/memset-1.c --target_board='unix{-m32\
-march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at skpgkp2 at gmail dot com)
