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/104492] [12 Regression] Bogus dangling pointer warning at -O3
Date: Wed, 16 Mar 2022 16:01:46 +0000 [thread overview]
Message-ID: <bug-104492-4-TAYHL3hqwt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104492-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104492
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
So the CLOBBER semantics correspond more closely to those of a C++ destructor
than to a deallocation call. It would be helpful to document these things.
next prev parent reply other threads:[~2022-03-16 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 19:35 [Bug c++/104492] New: Bogus dangling pointer warning (dangling pointer to ‘candidates’ may be used [-Werror=dangling-pointer=]) thiago at kde dot org
2022-02-10 20:08 ` [Bug c++/104492] " pinskia at gcc dot gnu.org
2022-02-11 0:49 ` [Bug middle-end/104492] [12 Regression] Bogus dangling pointer warning at -O3 msebor at gcc dot gnu.org
2022-02-11 0:59 ` msebor at gcc dot gnu.org
2022-02-11 9:06 ` rguenth at gcc dot gnu.org
2022-02-15 0:40 ` msebor at gcc dot gnu.org
2022-03-09 13:07 ` rguenth at gcc dot gnu.org
2022-03-09 13:07 ` rguenth at gcc dot gnu.org
2022-03-16 16:01 ` msebor at gcc dot gnu.org [this message]
2022-04-20 8:52 ` jakub at gcc dot gnu.org
2022-04-25 8:43 ` rguenth at gcc dot gnu.org
2022-04-27 10:03 ` cvs-commit at gcc dot gnu.org
2022-04-27 10:03 ` rguenth at gcc dot gnu.org
2022-04-27 16:48 ` cvs-commit 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-104492-4-TAYHL3hqwt@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).