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/109094] [13 Regression] ICE in -fanalyzer seen in qemu's target/i386/tcg/translate.c Date: Sat, 18 Mar 2023 16:49:08 +0000 [thread overview] Message-ID: <bug-109094-4-zp7m2qvic5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109094-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109094 --- Comment #9 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:430d7d88c1a123d787f529dbc29e6632c6e556fb commit r13-6749-g430d7d88c1a123d787f529dbc29e6632c6e556fb Author: David Malcolm <dmalcolm@redhat.com> Date: Sat Mar 18 12:48:01 2023 -0400 analyzer: fix ICE on certain longjmp calls [PR109094] PR analyzer/109094 reports an ICE in the analyzer seen on qemu's target/i386/tcg/translate.c The issue turned out to be that when handling a longjmp, the code to pop the frames was generating an svalue for the result_decl of any popped frame that had a non-void return type (and discarding it) leading to "uninit" poisoned_svalue_diagnostic instances being saved since the result_decl is only set by the greturn stmt. Later, when checking the feasibility of the path to these diagnostics, m_check_expr was evaluated in the context of the frame of the longjmp, leading to an attempt to evaluate the result_decl of each intervening frames whilst in the context of the topmost frame, leading to an assertion failure in frame_region::get_region_for_local here: 919 case RESULT_DECL: 920 gcc_assert (DECL_CONTEXT (expr) == m_fun->decl); 921 break; This patch updates the analyzer's longjmp implementation so that it doesn't attempt to generate svalues for the result_decls when popping frames, fixing the assertion failure (and presumably fixing "uninit" false positives in a release build). gcc/analyzer/ChangeLog: PR analyzer/109094 * region-model.cc (region_model::on_longjmp): Pass false for new "eval_return_svalue" param of pop_frame. (region_model::pop_frame): Add new "eval_return_svalue" param and use it to suppress the call to get_rvalue on the result when needed by on_longjmp. * region-model.h (region_model::pop_frame): Add new "eval_return_svalue" param. gcc/testsuite/ChangeLog: PR analyzer/109094 * gcc.dg/analyzer/setjmp-pr109094.c: New test. Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2023-03-18 16:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-10 20:00 [Bug analyzer/109094] New: " dmalcolm at gcc dot gnu.org 2023-03-10 20:10 ` [Bug analyzer/109094] " dmalcolm at gcc dot gnu.org 2023-03-13 8:53 ` rguenth at gcc dot gnu.org 2023-03-15 22:18 ` cvs-commit at gcc dot gnu.org 2023-03-16 8:45 ` marxin at gcc dot gnu.org 2023-03-16 13:00 ` dmalcolm at gcc dot gnu.org 2023-03-16 13:29 ` dmalcolm at gcc dot gnu.org 2023-03-17 22:11 ` dmalcolm at gcc dot gnu.org 2023-03-17 22:14 ` dmalcolm at gcc dot gnu.org 2023-03-17 23:07 ` dmalcolm at gcc dot gnu.org 2023-03-18 16:49 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-18 16:55 ` [Bug analyzer/109094] Uninit false positive from -fanalyzer when longjmp unwinds frames with return stmts dmalcolm at gcc dot gnu.org 2023-03-29 18:19 ` cvs-commit at gcc dot gnu.org 2023-03-29 19:11 ` 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-109094-4-zp7m2qvic5@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).