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, jwakely@redhat.com Subject: [r13-1139 Regression] FAIL: 21_strings/basic_string/cons/char/105995.cc (test for excess errors) on Linux/x86_64 Date: Thu, 16 Jun 2022 19:37:31 -0700 [thread overview] Message-ID: <20220617023731.A0F4D2864754@gskx-2.sc.intel.com> (raw) On Linux/x86_64, 98a0d72a610a87e8e383d366e50253ddcc9a51dd is the first bad commit commit 98a0d72a610a87e8e383d366e50253ddcc9a51dd Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jun 16 14:57:32 2022 +0100 libstdc++: Support constexpr global std::string for size < 15 [PR105995] caused FAIL: 21_strings/basic_string/cons/char/105995.cc (test for excess errors) with GCC configured with ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r13-1139/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=21_strings/basic_string/cons/char/105995.cc --target_board='unix{-m32}'" $ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=21_strings/basic_string/cons/char/105995.cc --target_board='unix{-m32\ -march=cascadelake}'" $ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=21_strings/basic_string/cons/char/105995.cc --target_board='unix{-m64}'" $ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=21_strings/basic_string/cons/char/105995.cc --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-06-17 2:37 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=20220617023731.A0F4D2864754@gskx-2.sc.intel.com \ --to=skpandey@sc.intel.com \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ --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).