public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/105017] [12 Regression] gcc/analyzer/sm-taint.cc:631:21: warning: private field 'm_mem_space' is not used [-Wunused-private-field] Date: Wed, 23 Mar 2022 12:37:58 +0000 [thread overview] Message-ID: <bug-105017-4-ugKw15wJv8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105017-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105017 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>: https://gcc.gnu.org/g:e6a3991ea15c0b14117b5693d77e15fd0477ce51 commit r12-7783-ge6a3991ea15c0b14117b5693d77e15fd0477ce51 Author: David Malcolm <dmalcolm@redhat.com> Date: Wed Mar 23 08:37:06 2022 -0400 analyzer: use tainted_allocation_size::m_mem_space [PR105017] gcc/analyzer/ChangeLog: PR analyzer/105017 * sm-taint.cc (taint_diagnostic::subclass_equal_p): Check m_has_bounds as well as m_arg. (tainted_allocation_size::subclass_equal_p): Chain up to base class implementation. Also check m_mem_space. (tainted_allocation_size::emit): Add note showing stack-based vs heap-based allocations. gcc/testsuite/ChangeLog: PR analyzer/105017 * gcc.dg/analyzer/taint-alloc-1.c: Add expected messages relating to heap vs stack. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-03-23 12:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-22 13:23 [Bug analyzer/105017] New: " marxin at gcc dot gnu.org 2022-03-22 13:23 ` [Bug analyzer/105017] [12 Regression] " marxin at gcc dot gnu.org 2022-03-22 18:50 ` dmalcolm at gcc dot gnu.org 2022-03-22 21:22 ` egallager at gcc dot gnu.org 2022-03-23 12:37 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-23 12:44 ` dmalcolm at gcc dot gnu.org 2022-03-23 13:25 ` marxin at gcc dot gnu.org
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=bug-105017-4-ugKw15wJv8@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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).