public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106119] [12 Regression] Bogus use-after-free warning triggered by optimizer
Date: Fri, 15 Mar 2024 01:23:10 +0000 [thread overview]
Message-ID: <bug-106119-4-zBmPXcyJtY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106119-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106119
Jeffrey A. Law <law at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[12/13/14 Regression] Bogus |[12 Regression] Bogus
|use-after-free warning |use-after-free warning
|triggered by optimizer |triggered by optimizer
CC| |law at gcc dot gnu.org
--- Comment #7 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Works with gcc-13 and the trunk. Adjusting regression markers.
prev parent reply other threads:[~2024-03-15 1:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 14:28 [Bug c/106119] New: " tom.cosgrove at arm dot com
2022-06-28 15:37 ` [Bug c/106119] " tom.cosgrove at arm dot com
2022-06-29 13:53 ` tom.cosgrove at arm dot com
2022-07-11 22:07 ` [Bug tree-optimization/106119] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-07-25 15:50 ` rguenth at gcc dot gnu.org
2022-10-17 12:31 ` rguenth at gcc dot gnu.org
2022-12-15 0:37 ` pinskia at gcc dot gnu.org
2023-05-08 12:24 ` [Bug tree-optimization/106119] [12/13/14 " rguenth at gcc dot gnu.org
2024-03-15 1:23 ` law at gcc dot gnu.org [this message]
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-106119-4-zBmPXcyJtY@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).