public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/110676] strlen of array[1] should not be optimized to 1 if using ASAN Date: Sat, 15 Jul 2023 18:32:39 +0000 [thread overview] Message-ID: <bug-110676-4-jLbgccZdxT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110676-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110676 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|builtin optimization |strlen of array[1] should |prevents ASan from |not be optimized to 1 if |detecting OOB reads |using ASAN Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2023-07-15 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. It is only an array of size 1 which is going to cause this issue. array of size 2 is always fine, e.g.: ``` #include <string.h> int main(void) { char s[2] = "AA"; return strlen(s); } ``` gives the expected error message.
next prev parent reply other threads:[~2023-07-15 18:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-15 18:28 [Bug sanitizer/110676] New: builtin optimization prevents ASan from detecting OOB reads nrk at disroot dot org 2023-07-15 18:32 ` pinskia at gcc dot gnu.org [this message] 2023-07-15 18:35 ` [Bug sanitizer/110676] [11/12/13/14 Regression] strlen of array[1] should not be optimized to 1 if using ASAN pinskia at gcc dot gnu.org 2023-07-15 18:35 ` nrk at disroot dot org 2024-02-05 20:23 ` [Bug sanitizer/110676] [11/12/13/14 Regression] strlen of array[1] should not be optimized to 0 " jakub at gcc dot gnu.org 2024-02-05 20:47 ` jakub at gcc dot gnu.org 2024-02-06 12:00 ` cvs-commit at gcc dot gnu.org 2024-02-06 12:01 ` [Bug sanitizer/110676] [11/12/13 " jakub at gcc dot gnu.org 2024-05-13 11:33 ` rguenth 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-110676-4-jLbgccZdxT@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).