From: David Malcolm <dmalcolm@redhat.com>
To: priour.be@gmail.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] analyzer: Fix regression bug after r14-1632-g9589a46ddadc8b [pr110198]
Date: Wed, 28 Jun 2023 19:36:42 -0400 [thread overview]
Message-ID: <e78d779d8607ec566cbb12199cddff7859a9ecd5.camel@redhat.com> (raw)
In-Reply-To: <20230622195522.1834793-1-vultkayn@gcc.gnu.org>
On Thu, 2023-06-22 at 21:55 +0200, priour.be@gmail.com wrote:
> From: benjamin priour <priour.be@gmail.com>
>
> Resend with proper subject line ...
>
> Hi,
Hi Benjamin
>
> Below is the fix to regression bug
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110198
> Was bootstrapped and regtested successfully on x86_64-linux-gnu
> Considering mishap from last patch, I'd would appreciate if you could
> also regtest it, to be sure :)
I tried this, but it didn't apply cleanly to my working copy. Which
version of master was this against / when did you last rebase this? I
see in comment #5 of PR 110198 that the results have been changing.
[...snip...]
> 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:
>
> * 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.
Something's gone a bit wrong with the formatting of the ChangeLog
entries. Ideally they shouldn't go wider than 74 columns, so they need
a few newlines. Also, some of the lines have too many leading tabs.
[...snip...]
The content of the patch itself looks reasonable.
Thanks
Dave
next prev parent reply other threads:[~2023-06-28 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 19:55 priour.be
2023-06-28 11:10 ` PING: " Benjamin Priour
2023-06-28 23:36 ` David Malcolm [this message]
2023-06-29 18:45 [PATCH] analyzer: Fix regression bug after r14-1632-g9589a46ddadc8b [PR110198] priour.be
2023-06-29 20:29 ` David Malcolm
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=e78d779d8607ec566cbb12199cddff7859a9ecd5.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=priour.be@gmail.com \
/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).