public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/108085] gcc trunk's ASAN at -O3 missed a stack-use-after-scope Date: Fri, 23 Dec 2022 15:25:17 +0000 [thread overview] Message-ID: <bug-108085-4-COS9cIWVBo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108085-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108085 --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> --- Created attachment 54153 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54153&action=edit pr108085.c.216t.uncprop1.dot.svg So no, it's a real issue where we optimize out .ASAN_CHECK (6, &f, 4, 8); in the exit block. As seen in the dump file, we have the very ASAN_CHECK in bb_3: .ASAN_CHECK (7, &f, 4, 8), however, there are 2 ASAN_MARK (POISON, &f, 4) calls that are on the path from bb_3 to the exit block. @Jakub: Can you please take a look at the optimization algorithm why the check is not preserved?
next prev parent reply other threads:[~2022-12-23 15:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-13 16:08 [Bug sanitizer/108085] New: " shaohua.li at inf dot ethz.ch 2022-12-14 8:26 ` [Bug sanitizer/108085] " marxin at gcc dot gnu.org 2022-12-14 8:27 ` rguenth at gcc dot gnu.org 2022-12-23 15:25 ` marxin at gcc dot gnu.org [this message] 2022-12-23 15:25 ` marxin at gcc dot gnu.org 2023-02-02 19:39 ` pinskia at gcc dot gnu.org 2023-02-02 19:45 ` pinskia 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-108085-4-COS9cIWVBo@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).