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, jason@redhat.com Subject: [r12-7287 Regression] FAIL: gcc.dg/deprecated.c (test for warnings, line 28) on Linux/x86_64 Date: Thu, 17 Feb 2022 19:45:43 -0800 [thread overview] Message-ID: <20220218034543.2307E2864701@gskx-2.sc.intel.com> (raw) On Linux/x86_64, 1b71bc7c8b18bd1b22debfde155f175fd1654942 is the first bad commit commit 1b71bc7c8b18bd1b22debfde155f175fd1654942 Author: Jason Merrill <jason@redhat.com> Date: Tue Feb 15 19:17:03 2022 -0500 tree: tweak warn_deprecated_use caused FAIL: gcc.dg/deprecated.c (test for excess errors) FAIL: gcc.dg/deprecated.c (test for warnings, line 28) with GCC configured with ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-7287/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=gcc.dg/deprecated.c --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/deprecated.c --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/deprecated.c --target_board='unix{-m64}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/deprecated.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-02-18 3: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=20220218034543.2307E2864701@gskx-2.sc.intel.com \ --to=skpandey@sc.intel.com \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ --cc=jason@redhat.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: linkBe 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).