public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vanyacpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/99418] sanitizer checks for accessing multidimentional VLA-array
Date: Tue, 09 Mar 2021 08:47:20 +0000 [thread overview]
Message-ID: <bug-99418-4-vumDwDUKZz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99418-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99418
--- Comment #7 from Ivan Sorokin <vanyacpp at gmail dot com> ---
(In reply to Martin Liška from comment #3)
> That said, can we close it as resolved?
I'm sorry for not being clear from the beginning. The original report was about
-fsanitize=bounds sanitizer which sometimes allows accessing one past the end
element.
Now after #c4 I see that language rules make it excessively complicated for
compiler to do this.
I believe that one past the end is important error to check for, but I
understand why compilers might choose to avoid doing it. Feel free to close the
issue if implementing it is infeasible.
next prev parent reply other threads:[~2021-03-09 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 19:11 [Bug sanitizer/99418] New: " vanyacpp at gmail dot com
2021-03-06 22:53 ` [Bug sanitizer/99418] " vanyacpp at gmail dot com
2021-03-07 7:44 ` vanyacpp at gmail dot com
2021-03-08 9:15 ` marxin at gcc dot gnu.org
2021-03-08 10:14 ` jakub at gcc dot gnu.org
2021-03-08 18:23 ` msebor at gcc dot gnu.org
2021-03-09 8:39 ` vanyacpp at gmail dot com
2021-03-09 8:47 ` vanyacpp at gmail dot com [this message]
2021-03-09 8:54 ` vanyacpp at gmail dot com
2021-03-09 15:48 ` [Bug sanitizer/99418] more cases where -fsanitize=bounds can check one-past-the-end accesses msebor 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-99418-4-vumDwDUKZz@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).