public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/104075] New: bogus/missing -Wuse-after-free
Date: Mon, 17 Jan 2022 21:56:33 +0000 [thread overview]
Message-ID: <bug-104075-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104075
Bug ID: 104075
Summary: bogus/missing -Wuse-after-free
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
This meta-bug tracks false positives and negatives in the middle-end
-Wuse-after-free, new in GCC 12 (unrelated to -Wanalyzer-use-after-free).
next reply other threads:[~2022-01-17 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 21:56 msebor at gcc dot gnu.org [this message]
2022-01-17 21:57 ` [Bug middle-end/104075] " msebor at gcc dot gnu.org
2022-01-26 17:23 ` mpolacek at gcc dot gnu.org
2022-01-31 15:46 ` msebor at gcc dot gnu.org
2022-01-31 19:08 ` msebor at gcc dot gnu.org
2022-12-15 0:37 ` pinskia at gcc dot gnu.org
2022-12-15 0:40 ` pinskia at gcc dot gnu.org
2023-03-16 7:30 ` rguenth at gcc dot gnu.org
2023-03-21 8:22 ` rguenth at gcc dot gnu.org
2023-11-15 22:36 ` xry111 at gcc dot gnu.org
2024-04-18 23:50 ` 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-104075-4@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).