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/108725] -Wanalyzer-use-of-uninitialized-value on ternary pointer access seen in qemu-7.2.0's dump/win_dump.c
Date: Wed, 15 Feb 2023 19:53:51 +0000	[thread overview]
Message-ID: <bug-108725-4-MfbBskq8Nk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108725-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108725

--- Comment #1 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:b03a10b0b25cef4928ccead4c8a461d3674dbe86

commit r13-6064-gb03a10b0b25cef4928ccead4c8a461d3674dbe86
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Wed Feb 15 14:52:02 2023 -0500

    analyzer: fix uninit false +ves [PR108664,PR108666,PR108725]

    This patch updates poisoned_value_diagnostic so that, where possible,
    it checks to see if the value is still poisoned along the execution
    path seen during feasibility analysis, rather than just that seen
    in the exploded graph.

    Integration testing shows this reduction in the number of
    false positives:
      -Wanalyzer-use-of-uninitialized-value: 191 -> 153 (-38)
    where the changes happen in:
          coreutils-9.1: 34 -> 20 (-14)
             qemu-7.2.0: 78 -> 54 (-24)

    gcc/analyzer/ChangeLog:
            PR analyzer/108664
            PR analyzer/108666
            PR analyzer/108725
            * diagnostic-manager.cc (epath_finder::get_best_epath): Add
            "target_stmt" param.
            (epath_finder::explore_feasible_paths): Likewise.
            (epath_finder::process_worklist_item): Likewise.
            (saved_diagnostic::calc_best_epath): Pass m_stmt to
            epath_finder::get_best_epath.
            * engine.cc (feasibility_state::maybe_update_for_edge): Move
            per-stmt logic to...
            (feasibility_state::update_for_stmt): ...this new function.
            * exploded-graph.h (feasibility_state::update_for_stmt): New decl.
            * feasible-graph.cc (feasible_node::get_state_at_stmt): New.
            * feasible-graph.h: Include "analyzer/exploded-graph.h".
            (feasible_node::get_state_at_stmt): New decl.
            * infinite-recursion.cc
            (infinite_recursion_diagnostic::check_valid_fpath_p): Update for
            vfunc signature change.
            * pending-diagnostic.h (pending_diagnostic::check_valid_fpath_p):
            Convert first param to a reference.  Add stmt param.
            * region-model.cc: Include "analyzer/feasible-graph.h".
            (poisoned_value_diagnostic::poisoned_value_diagnostic): Add
            "check_expr" param.
            (poisoned_value_diagnostic::check_valid_fpath_p): New.
            (poisoned_value_diagnostic::m_check_expr): New field.
            (region_model::check_for_poison): Attempt to supply a check_expr
            to the diagnostic
            (region_model::deref_rvalue): Add NULL for new check_expr param
            of poisoned_value_diagnostic.
            (region_model::get_or_create_region_for_heap_alloc): Don't reuse
            regions that are marked as TOUCHED.

    gcc/testsuite/ChangeLog:
            PR analyzer/108664
            PR analyzer/108666
            PR analyzer/108725
            * gcc.dg/analyzer/coreutils-cksum-pr108664.c: New test.
            * gcc.dg/analyzer/coreutils-sum-pr108666.c: New test.
            * gcc.dg/analyzer/torture/uninit-pr108725.c: New test.

    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

  reply	other threads:[~2023-02-15 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 19:57 [Bug analyzer/108725] New: " dmalcolm at gcc dot gnu.org
2023-02-15 19:53 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-15 20:00 ` [Bug analyzer/108725] " dmalcolm 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-108725-4-MfbBskq8Nk@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: link
Be 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).