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/110198] [14 regression] g++.dg/analyzer/pr100244.C fails after r14-1632-g9589a46ddadc8b Date: Thu, 29 Jun 2023 23:35:21 +0000 [thread overview] Message-ID: <bug-110198-4-F1zkQz4Ahw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110198-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110198 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Benjamin Priour <vultkayn@gcc.gnu.org>: https://gcc.gnu.org/g:1eb90f46c16453f72dc119ba20b07053a15b452d commit r14-2203-g1eb90f46c16453f72dc119ba20b07053a15b452d Author: benjamin priour <priour.be@gmail.com> Date: Thu Jun 22 21:39:05 2023 +0200 analyzer: Fix regression bug after r14-1632-g9589a46ddadc8b [PR110198] g++.dg/analyzer/PR100244.C was failing after a patch of PR109439. The reason was a spurious preemptive return of get_store_value upon out-of-bounds read that was preventing further checks. Now instead, a boolean value check_poisoned goes to false when a OOB is detected, and is later on given to get_or_create_initial_value. gcc/analyzer/ChangeLog: PR analyzer/110198 * region-model-manager.cc (region_model_manager::get_or_create_initial_value): Take an optional boolean value to bypass poisoning checks * region-model-manager.h: Update declaration of the above function. * region-model.cc (region_model::get_store_value): No longer returns on OOB, but rather gives a boolean to get_or_create_initial_value. (region_model::check_region_access): Update docstring. (region_model::check_region_for_write): Update docstring. Signed-off-by: benjamin priour <priour.be@gmail.com>
next prev parent reply other threads:[~2023-06-29 23:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-09 19:13 [Bug other/110198] New: " seurer at gcc dot gnu.org 2023-06-09 22:12 ` [Bug other/110198] " pinskia at gcc dot gnu.org 2023-06-09 22:30 ` [Bug analyzer/110198] " vultkayn at gcc dot gnu.org 2023-06-20 14:37 ` hp at gcc dot gnu.org 2023-06-20 14:45 ` priour.be at gmail dot com 2023-06-22 14:33 ` hp at gcc dot gnu.org 2023-06-29 23:35 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-29 23:39 ` vultkayn 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-110198-4-F1zkQz4Ahw@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).