public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/105382] Support for coroutines in -fanalyzer Date: Tue, 26 Apr 2022 12:25:37 +0000 [thread overview] Message-ID: <bug-105382-4-fA75rv9sBu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105382-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105382 --- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Looks like the analyzer is assuming that all of the different _Coro_resume_index values are possible at each entry to f(f()::_Z1fv.Frame*), but AIUI that value is expressing which basic block the coroutine is re-entering i.e. this data value exists to affect control flow. Presumably that ought to be expressed in the exploded graph, so that it properly respects control flow. So I think we need to be smarter about _Coro_resume_index values in various ways e.g. not merge state for them, and assume some initial value for the initial entry to the coroutine, etc.
next prev parent reply other threads:[~2022-04-26 12:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-25 19:25 [Bug analyzer/105382] New: " dmalcolm at gcc dot gnu.org 2022-04-26 12:25 ` dmalcolm at gcc dot gnu.org [this message] 2022-11-02 18:12 ` [Bug analyzer/105382] " pinskia 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-105382-4-fA75rv9sBu@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).