public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tlange at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/106203] New: Allow to emit diagnostics at return edges for the exit point as well as the call site Date: Tue, 05 Jul 2022 17:49:00 +0000 [thread overview] Message-ID: <bug-106203-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106203 Bug ID: 106203 Summary: Allow to emit diagnostics at return edges for the exit point as well as the call site Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: tlange at gcc dot gnu.org Target Milestone: --- Currently, the region_model_context at return edges, created inside program_state::on_edge, neither holds a stmt nor a stmt_finder and thus, warnings at return edges are rejected by impl_region_model_context::warn. PR105900 has 2 XFAILs inside allocation-size-(1|2).c because the call to set_value (lhs, <returned_value>) happens at a return edge. Similarly, PR105888 also needs to emit a warning at a return edge, but for the callee's exit point. David already expressed ideas on how to solve this: - have two contexts for pop_frame: one in the old frame, the other in the new frame (for the caller) - generalize stmt_finder, so it can also update the supernode to use - rework pop_frame (I've had to do this before, I've run into issues like this before).
next reply other threads:[~2022-07-05 17:49 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-05 17:49 tlange at gcc dot gnu.org [this message] 2022-08-10 13:45 ` [Bug analyzer/106203] " dmalcolm at gcc dot gnu.org 2024-06-01 17:57 ` cvs-commit at gcc dot gnu.org 2024-06-01 18:31 ` 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-106203-4@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).