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++/112335] missed optimization on reset and assign unique_ptr
Date: Thu, 02 Nov 2023 07:30:57 +0000	[thread overview]
Message-ID: <bug-112335-4-ofPmEdODGo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112335-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Federico Kircheis from comment #2)
> > Well s::~s could touch the reference std::unique_ptr<s> (ps1).
> 
> In both cases, s::~s is called only once.
> 
> Also during the move-assignment no user-provided-code is involved (except
> the destruction of ps1, and even case of a user-provided deleter, it is only
> called if the pointer is not nullptr.

NO. NO.


std::unique_ptr<s> t;

__thread bool tt;
inline s::~s()
{
  if (tt)
    return;
  tt = true;
  t.reset(new s);
  tt = false;
}

Is still a valid ~s as far as I can tell.
Yes it is odd but so what it is still valid.

Now will anyone write code like this, doubt it.

Also note clang does not optimize this with either libstdc++ or libc++.

  parent reply	other threads:[~2023-11-02  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 13:26 [Bug c++/112335] New: " federico at kircheis dot it
2023-11-01 15:51 ` [Bug c++/112335] " pinskia at gcc dot gnu.org
2023-11-02  7:17 ` federico at kircheis dot it
2023-11-02  7:19 ` federico at kircheis dot it
2023-11-02  7:30 ` pinskia at gcc dot gnu.org [this message]
2023-11-02  8:01 ` federico at kircheis dot it
2023-11-02 17:23 ` redi at gcc dot gnu.org
2023-11-03  8:06 ` federico at kircheis dot it
2023-11-03  9:10 ` redi at gcc dot gnu.org
2023-11-03 10:23 ` federico at kircheis dot it
2023-11-03 14:23 ` redi 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-112335-4-ofPmEdODGo@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).