public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ygribov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/106558] ASan failed to detect a global-buffer-overflow
Date: Mon, 15 Aug 2022 11:03:36 +0000 [thread overview]
Message-ID: <bug-106558-4-NgvCnzRlJv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106558-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106558
--- Comment #10 from Yury Gribov <ygribov at gcc dot gnu.org> ---
Created attachment 53458
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53458&action=edit
Very draft patch
(In reply to Jakub Jelinek from comment #7)
> Perhaps either a quick check that for base ptrs that live in memory
> gimple_vuse is the same for both statements or if not, do walk_aliased_vdefs
> with low constant limit?
> We'd want to stop if we reach the vdef of the stmt in base_checks vector
> (then we didn't find anything that could clobber it and can therefore use
> the cached check) or when we see a stmt that may clobber it (then we can't
> use the cached check).
Something like this? It does not help with b.1_2 in attached reprocase though,
because alias oracle considers
*b.0_1 = 2;
to clobber it.
I'm trying to collect statistics how many checks this optimization removes
during bootstrap-asan but I'm getting crashes when asan-bootstrapping on
unchanged trunk. Is this possible?
next prev parent reply other threads:[~2022-08-15 11:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 12:05 [Bug sanitizer/106558] New: " shaohua.li at inf dot ethz.ch
2022-08-09 0:30 ` [Bug sanitizer/106558] " pinskia at gcc dot gnu.org
2022-08-09 12:30 ` marxin at gcc dot gnu.org
2022-08-10 9:20 ` jakub at gcc dot gnu.org
2022-08-10 9:35 ` jakub at gcc dot gnu.org
2022-08-10 9:49 ` tetra2005 at gmail dot com
2022-08-10 9:51 ` jakub at gcc dot gnu.org
2022-08-10 10:13 ` jakub at gcc dot gnu.org
2022-08-11 14:32 ` tetra2005 at gmail dot com
2022-08-11 15:01 ` jakub at gcc dot gnu.org
2022-08-15 11:03 ` ygribov at gcc dot gnu.org [this message]
2022-09-02 3:38 ` ygribov at gcc dot gnu.org
2022-09-02 3:38 ` ygribov at gcc dot gnu.org
2022-09-13 13:56 ` tetra2005 at gmail dot com
2022-11-07 9:14 ` shaohua.li at inf dot ethz.ch
2022-11-21 9:48 ` marxin at gcc dot gnu.org
2022-11-21 9:49 ` marxin at gcc dot gnu.org
2022-11-21 11:50 ` tetra2005 at gmail dot com
2022-11-22 12:21 ` marxin at gcc dot gnu.org
2022-11-28 9:49 ` cvs-commit at gcc dot gnu.org
2022-11-28 9:52 ` marxin at gcc dot gnu.org
2022-12-02 12:51 ` marxin 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-106558-4-NgvCnzRlJv@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: 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).