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/99771] Analyzer diagnostics should not say "<unknown>"
Date: Wed, 31 Mar 2021 23:18:00 +0000	[thread overview]
Message-ID: <bug-99771-4-2on5zYvzoI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99771-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:e4bb1bd60a9fd1bed36092a990aa5fed5d45bfa6

commit r11-7941-ge4bb1bd60a9fd1bed36092a990aa5fed5d45bfa6
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Mon Mar 29 16:13:32 2021 -0400

    analyzer: avoid printing '<unknown>' for SSA names [PR99771]

    We don't want to print '<unknown>' in our diagnostics, but
    PR analyzer/99771 lists various cases where -fanalyzer does, due to
    using the SSA_NAME for a temporary when determining the best tree to
    use.

    This can happen in two ways:

    (a) ...when a better expression than the SSA_NAME could be built, but
    finding it requires traversing the relationships in the region_model
    in a graph-like way, rather than by considering individual svalues and
    regions.

    (b) ...when the only remaining user of the underlying svalue is the
    SSA_NAME, typically due to the diagnostic referring to a temporary.

    I've been experimenting with fixing (a), but don't have a good fix yet.
    In the meantime, this patch addresses (b) by detecting if we have
    the SSA_NAME for a temporary, and, for the cases where it's possible,
    reconstructing a tree by walking the def-stmts.  This fixes various
    cases of (b) and ameliorates some cases of (a).

    gcc/analyzer/ChangeLog:
            PR analyzer/99771
            * analyzer.cc (maybe_reconstruct_from_def_stmt): New.
            (fixup_tree_for_diagnostic_1): New.
            (fixup_tree_for_diagnostic): New.
            * analyzer.h (fixup_tree_for_diagnostic): New decl.
            * checker-path.cc (call_event::get_desc): Call
            fixup_tree_for_diagnostic and use it for the call_with_state call.
            (warning_event::get_desc): Likewise for the final_event and
            make_label_text calls.
            * engine.cc (impl_region_model_context::on_state_leak): Likewise
            for the on_leak and add_diagnostic calls.
            * region-model.cc (region_model::get_representative_tree):
            Likewise for the result.

    gcc/testsuite/ChangeLog:
            PR analyzer/99771
            * gcc.dg/analyzer/data-model-10.c: Update expected output.
            * gcc.dg/analyzer/malloc-ipa-13.c: Likewise.
            * gcc.dg/analyzer/malloc-ipa-13a.c: New test.
            * gcc.dg/analyzer/pr99771-1.c: New test.

  parent reply	other threads:[~2021-03-31 23:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 15:26 [Bug analyzer/99771] New: " dmalcolm at gcc dot gnu.org
2021-03-25 15:26 ` [Bug analyzer/99771] " dmalcolm at gcc dot gnu.org
2021-03-30 21:52 ` cvs-commit at gcc dot gnu.org
2021-03-31 23:18 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-31 23:21 ` dmalcolm at gcc dot gnu.org
2022-03-07 19:21 ` cvs-commit at gcc dot gnu.org
2022-03-08 19:17 ` 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-99771-4-2on5zYvzoI@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).