public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cheyenne.wills at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110501] Invalid use-after-free / realloc with a store/load happening Date: Thu, 06 Jul 2023 20:49:57 +0000 [thread overview] Message-ID: <bug-110501-4-jARlNP7Ka1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110501-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110501 --- Comment #6 from Cheyenne Wills <cheyenne.wills at gmail dot com> --- Just another bit of information. Specifying just -Werror=use-after-free appears to be not not enough to trigger the problem. Using -Wall however does trigger the problem. (tried on gcc-12 and gcc-13)
next prev parent reply other threads:[~2023-07-06 20:49 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-30 15:10 [Bug analyzer/110501] New: Invalid use-after-free / realloc cheyenne.wills at gmail dot com 2023-06-30 15:11 ` [Bug analyzer/110501] " cheyenne.wills at gmail dot com 2023-06-30 16:10 ` [Bug tree-optimization/110501] Invalid use-after-free / realloc at -O0 pinskia at gcc dot gnu.org 2023-06-30 16:12 ` [Bug tree-optimization/110501] Invalid use-after-free / realloc with a store/load happening pinskia at gcc dot gnu.org 2023-06-30 16:16 ` cheyenne.wills at gmail dot com 2023-07-03 6:24 ` rguenth at gcc dot gnu.org 2023-07-06 20:49 ` cheyenne.wills at gmail dot com [this message] 2023-10-31 16:18 ` jhb at FreeBSD dot org 2024-03-10 14:03 ` [Bug tree-optimization/110501] [13/14 regression] Invalid -Wuse-after-free " sjames at gcc dot gnu.org 2024-04-04 7:39 ` rguenth at gcc dot gnu.org 2024-04-04 7:39 ` rguenth at gcc dot gnu.org 2024-05-21 9:16 ` [Bug tree-optimization/110501] [13/14/15 " jakub 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-110501-4-jARlNP7Ka1@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).