public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109671] Spurious dangling reference warning in GCC 13
Date: Fri, 19 Jan 2024 17:35:47 +0000 [thread overview]
Message-ID: <bug-109671-4-gUCrW4lMVf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109671-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109671
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
CC| |mpolacek at gcc dot gnu.org
Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Patrick J. LoPresti from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > There is no way for GCC to know that get_foo_by_name does not store the
> > argument into what is returned so it warns about this case ...
>
> To summarize:
>
> GCC is warning because it does not and cannot know whether I am managing
> object lifetimes correctly.
>
> The only way to silence the warning is to modify my code to make it uglier,
> into a form where GCC still does not and cannot know whether I am managing
> lifetimes correctly.
>
> So is this a valid bug report, or not?
It's valid but also I don't think I can tweak the heuristic not to warn here.
There ought to be a simpler way to suppress the warning, see bug 109642.
*** This bug has been marked as a duplicate of bug 109642 ***
prev parent reply other threads:[~2024-01-19 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 17:48 [Bug c++/109671] New: " lopresti at gmail dot com
2023-04-28 17:51 ` [Bug c++/109671] " pinskia at gcc dot gnu.org
2023-04-28 19:31 ` lopresti at gmail dot com
2023-05-01 1:15 ` lopresti at gmail dot com
2023-05-02 19:50 ` cvs-commit at gcc dot gnu.org
2024-01-19 17:35 ` mpolacek 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-109671-4-gUCrW4lMVf@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).