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-1243 Regression] FAIL: gcc.dg/torture/pr106070.c   -Os execution test on Linux/x86_64
Date: Fri, 24 Jun 2022 11:20:41 -0700	[thread overview]
Message-ID: <20220624182041.45A0F2864754@gskx-2.sc.intel.com> (raw)

On Linux/x86_64,

b36a1c964f99758de1f3b169628965d3c3af812b is the first bad commit
commit b36a1c964f99758de1f3b169628965d3c3af812b
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Jun 24 13:37:22 2022 +0200

    middle-end/106070 - bogus cond-expr folding

caused

FAIL: gcc.dg/torture/pr106070.c   -O0  execution test
FAIL: gcc.dg/torture/pr106070.c   -O1  execution test
FAIL: gcc.dg/torture/pr106070.c   -O2  execution test
FAIL: gcc.dg/torture/pr106070.c   -O2 -flto -fno-use-linker-plugin -flto-partition=none  execution test
FAIL: gcc.dg/torture/pr106070.c   -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects  execution test
FAIL: gcc.dg/torture/pr106070.c   -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions  execution test
FAIL: gcc.dg/torture/pr106070.c   -O3 -g  execution test
FAIL: gcc.dg/torture/pr106070.c   -Os  execution test

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r13-1243/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="dg-torture.exp=gcc.dg/torture/pr106070.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg-torture.exp=gcc.dg/torture/pr106070.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)


                 reply	other threads:[~2022-06-24 18:20 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=20220624182041.45A0F2864754@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).