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, mail@tim-lange.me Subject: [r13-2029 Regression] FAIL: gcc.dg/analyzer/torture/pr93451.c -Os (test for excess errors) on Linux/x86_64 Date: Sat, 13 Aug 2022 04:17:57 +0800 [thread overview] Message-ID: <202208122017.27CKHvIp3108482@shliclel314.sh.intel.com> (raw) On Linux/x86_64, 7e3b45befdbbf1a1f9ff728fa2bac31b4756907c is the first bad commit commit 7e3b45befdbbf1a1f9ff728fa2bac31b4756907c Author: Tim Lange <mail@tim-lange.me> Date: Fri Aug 12 10:27:16 2022 +0200 analyzer: out-of-bounds checker [PR106000] caused FAIL: gcc.dg/analyzer/torture/pr93451.c -O0 (test for excess errors) FAIL: gcc.dg/analyzer/torture/pr93451.c -O1 (test for excess errors) FAIL: gcc.dg/analyzer/torture/pr93451.c -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors) FAIL: gcc.dg/analyzer/torture/pr93451.c -O2 (test for excess errors) FAIL: gcc.dg/analyzer/torture/pr93451.c -O3 -g (test for excess errors) FAIL: gcc.dg/analyzer/torture/pr93451.c -Os (test for excess errors) with GCC configured with ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-2029/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="analyzer-torture.exp=gcc.dg/analyzer/torture/pr93451.c --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer-torture.exp=gcc.dg/analyzer/torture/pr93451.c --target_board='unix{-m32\ -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-08-12 20:18 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=202208122017.27CKHvIp3108482@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=mail@tim-lange.me \ /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).