public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com> To: haochen.jiang@intel.com, gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org, jwakely@redhat.com Subject: [r13-2303 Regression] FAIL: g++.dg/tree-ssa/empty-loop.C -std=gnu++20 (test for excess errors) on Linux/x86_64 Date: Thu, 01 Sep 2022 09:39:37 +0800 [thread overview] Message-ID: <202209010139.2811dbRe3591685@shliclel314.sh.intel.com> (raw) On Linux/x86_64, b911ca4231a366ddfd026f190b126bd517f4e640 is the first bad commit commit b911ca4231a366ddfd026f190b126bd517f4e640 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Aug 26 16:22:21 2022 +0100 libstdc++: Add [[nodiscard]] attribute to <string> and <string_view> caused FAIL: g++.dg/tree-ssa/empty-loop.C -std=gnu++17 (test for excess errors) FAIL: g++.dg/tree-ssa/empty-loop.C -std=gnu++20 (test for excess errors) with GCC configured with ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-2303/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/tree-ssa/empty-loop.C --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/tree-ssa/empty-loop.C --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/tree-ssa/empty-loop.C --target_board='unix{-m64}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=g++.dg/tree-ssa/empty-loop.C --target_board='unix{-m64\ -march=cascadelake}'" (Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com)
reply other threads:[~2022-09-01 1:39 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=202209010139.2811dbRe3591685@shliclel314.sh.intel.com \ --to=haochenj@ecsmtp.sh.intel.com \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ --cc=haochen.jiang@intel.com \ --cc=jwakely@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).