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/108968] fanalyzer false positive with the uninitalised-ness of the stack pointer Date: Thu, 02 Mar 2023 19:02:31 +0000 [thread overview] Message-ID: <bug-108968-4-6ZWTgkHmRI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108968 --- Comment #7 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:20bd258d0fa09837b3a93478ef92d8789cbcd442 commit r13-6420-g20bd258d0fa09837b3a93478ef92d8789cbcd442 Author: David Malcolm <dmalcolm@redhat.com> Date: Thu Mar 2 14:01:19 2023 -0500 analyzer: fix uninit false +ves reading from DECL_HARD_REGISTER [PR108968] gcc/analyzer/ChangeLog: PR analyzer/108968 * region-model.cc (region_model::get_rvalue_1): Handle VAR_DECLs with a DECL_HARD_REGISTER by returning UNKNOWN. gcc/testsuite/ChangeLog: PR analyzer/108968 * gcc.dg/analyzer/uninit-pr108968-register.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-03-02 19:02 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 12:41 [Bug c/108968] New: " andrew.cooper3 at citrix dot com 2023-02-28 13:12 ` [Bug c/108968] " schwab@linux-m68k.org 2023-02-28 13:44 ` andrew.cooper3 at citrix dot com 2023-02-28 13:59 ` schwab@linux-m68k.org 2023-02-28 15:41 ` andrew.cooper3 at citrix dot com 2023-02-28 18:56 ` [Bug analyzer/108968] " dmalcolm at gcc dot gnu.org 2023-02-28 19:04 ` andrew.cooper3 at citrix dot com 2023-03-02 19:02 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-02 19:25 ` dmalcolm at gcc dot gnu.org 2023-03-02 21:15 ` andrew.cooper3 at citrix dot com 2023-03-02 21:20 ` andrew.cooper3 at citrix dot com 2023-03-02 21:25 ` dmalcolm at gcc dot gnu.org 2023-03-02 21:29 ` dmalcolm at gcc dot gnu.org 2023-03-02 21:34 ` andrew.cooper3 at citrix dot com 2023-03-02 21:35 ` andrew.cooper3 at citrix dot com 2023-03-02 21:41 ` andrew.cooper3 at citrix dot com 2023-03-02 21:46 ` dmalcolm at gcc dot gnu.org 2023-03-02 21:48 ` dmalcolm at gcc dot gnu.org 2023-03-02 21:52 ` dmalcolm at gcc dot gnu.org 2023-03-29 18:19 ` cvs-commit 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-108968-4-6ZWTgkHmRI@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).