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/108637] ASAN at -O2 misses a stack-use-after-scope Date: Thu, 02 Feb 2023 19:33:29 +0000 [thread overview] Message-ID: <bug-108637-4-z4QZmUNycG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108637-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108637 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- PRE removes the load/stores from/to *f . Basically the compiler is able to remove the use-after-scope usage with -O2 and above.
next prev parent reply other threads:[~2023-02-02 19:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-02 12:10 [Bug sanitizer/108637] New: " shaohua.li at inf dot ethz.ch 2023-02-02 19:33 ` pinskia at gcc dot gnu.org [this message] 2023-02-02 21:51 ` [Bug sanitizer/108637] " shaohua.li at inf dot ethz.ch 2023-02-02 22:06 ` shaohua.li at inf dot ethz.ch 2023-02-03 13:32 ` 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-108637-4-z4QZmUNycG@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).