public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: skpandey@sc.intel.com
To: gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org, rguenther@suse.de
Subject: [r13-1450 Regression] FAIL: 25_algorithms/find_end/constrained.cc (test for excess errors) on Linux/x86_64
Date: Mon, 04 Jul 2022 12:09:38 -0700	[thread overview]
Message-ID: <20220704190938.1EC5F2864754@gskx-2.sc.intel.com> (raw)

On Linux/x86_64,

d2a898666609452ef79a14feae1cadc3538e4b45 is the first bad commit
commit d2a898666609452ef79a14feae1cadc3538e4b45
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Jun 21 16:17:58 2022 +0200

    Put virtual operands into loop-closed SSA

caused

FAIL: 25_algorithms/find_end/constrained.cc (test for excess errors)
FAIL: gcc.dg/auto-init-uninit-4.c (test for excess errors)

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r13-1450/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/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=25_algorithms/find_end/constrained.cc --target_board='unix{-m64}'"
$ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=25_algorithms/find_end/constrained.cc --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/auto-init-uninit-4.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/auto-init-uninit-4.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/auto-init-uninit-4.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/auto-init-uninit-4.c --target_board='unix{-m64\ -march=cascadelake}'"

(Please do not reply to this email, for question about this report, contact me at skpgkp2 at gmail dot com)


                 reply	other threads:[~2022-07-04 19:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220704190938.1EC5F2864754@gskx-2.sc.intel.com \
    --to=skpandey@sc.intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).