public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114220] False positive warning: possibly dangling reference to a temporary [-Wdangling-reference]
Date: Sun, 03 Mar 2024 18:37:13 +0000	[thread overview]
Message-ID: <bug-114220-4-Ucm7ih6Y96@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114220-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114220

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Дилян Палаузов from comment #3)
> > The warning is designed this way explictly because you are returning a reference and taking a reference as an argument and in the case of b2, the tempory is `std::string("u")` .
> 
> > In GCC 14+ (since r14-9263-gc7607c4cf18986), you can add [[gnu::no_dangling]] to the z2 function definition to mark it as not returning a dangling reference (from the arguments). and the warning goes away.
> 
> If the declaration and definitions are in different files, do I have to add
> [[gnu::no_dangling]] only to the function declaration ?

Yes only on the declaration is needed.

> 
> That said, is the warning triggered only based on the function declaration
> (accepting as parameter a reference to temporary and returning a reference),
> when on the function invocation the parameter is indeed a reference to a
> temporary?

Yes that is correct, it is based on the function declaration only and the
warning does not look into the function to see it does not return the a
referenced based on the reference being passed.

  parent reply	other threads:[~2024-03-03 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03  8:26 [Bug c++/114220] New: " dilyan.palauzov at aegee dot org
2024-03-03  8:33 ` [Bug c++/114220] " pinskia at gcc dot gnu.org
2024-03-03 10:23 ` dilyan.palauzov at aegee dot org
2024-03-03 10:30 ` dilyan.palauzov at aegee dot org
2024-03-03 18:37 ` pinskia at gcc dot gnu.org [this message]
2024-03-04  9:07 ` xry111 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-114220-4-Ucm7ih6Y96@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).