public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "sunil.k.pandey" <skpandey@sc.intel.com>
To: gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org,
	roger@nextmovesoftware.com
Subject: [r12-7607 Regression] FAIL: g++.dg/other/pr84964.C  -std=c++98 (test for warnings, line 6) on Linux/x86_64
Date: Thu, 10 Mar 2022 20:45:56 -0800	[thread overview]
Message-ID: <20220311044556.59B762864701@gskx-2.sc.intel.com> (raw)

On Linux/x86_64,

a717376e99fb33ba3b06bd8122e884f4b63a60c9 is the first bad commit
commit a717376e99fb33ba3b06bd8122e884f4b63a60c9
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Thu Mar 10 23:49:15 2022 +0000

    PR c++/84964: Middle-end patch to expand_call for ICE after sorry.

caused

FAIL: g++.dg/other/pr84964.C  -std=c++14  (test for warnings, line 6)
FAIL: g++.dg/other/pr84964.C  -std=c++17  (test for warnings, line 6)
FAIL: g++.dg/other/pr84964.C  -std=c++20  (test for warnings, line 6)
FAIL: g++.dg/other/pr84964.C  -std=c++98  (test for warnings, line 6)

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-7607/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.exp=g++.dg/other/pr84964.C --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/other/pr84964.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-03-11  4:45 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=20220311044556.59B762864701@gskx-2.sc.intel.com \
    --to=skpandey@sc.intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=roger@nextmovesoftware.com \
    /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).