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, mail@tim-lange.me Subject: [r13-1405 Regression] FAIL: gcc.dg/analyzer/allocation-size-4.c warning at line 31 (test for warnings, line 28) on Linux/x86_64 Date: Sat, 02 Jul 2022 14:10:52 -0700 [thread overview] Message-ID: <20220702211052.501C42864754@gskx-2.sc.intel.com> (raw) On Linux/x86_64, e6c3bb379f515b27268d08e62b4b3e5d7200b437 is the first bad commit commit e6c3bb379f515b27268d08e62b4b3e5d7200b437 Author: Tim Lange <mail@tim-lange.me> Date: Fri Jul 1 00:02:17 2022 +0200 analyzer: add allocation size checker [PR105900] caused FAIL: gcc.dg/analyzer/allocation-size-4.c note at line 32 (test for warnings, line 28) FAIL: gcc.dg/analyzer/allocation-size-4.c note at line 33 (test for warnings, line 28) FAIL: gcc.dg/analyzer/allocation-size-4.c warning at line 31 (test for warnings, line 28) with GCC configured with ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r13-1405/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.exp=gcc.dg/analyzer/allocation-size-4.c --target_board='unix{-m32}'" $ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/allocation-size-4.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)
next reply other threads:[~2022-07-02 21:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-02 21:10 skpandey [this message] 2022-07-02 23:20 ` [PATCH] analyzer: Use fixed-width types in allocation size tests Tim Lange 2022-07-02 23:38 ` David Malcolm 2022-07-03 19:31 ` David Malcolm
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=20220702211052.501C42864754@gskx-2.sc.intel.com \ --to=skpandey@sc.intel.com \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ --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).