public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Maged Michael <maged.michael@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
	gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Fix aliasing violation in std::shared_ptr
Date: Sun, 23 Jan 2022 23:46:40 -0500	[thread overview]
Message-ID: <CABBFi08J5MTckPu+NaYrcs9AU5C0X5NGdqtQiMw7=noB3jDqxQ@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4kCsS5LAuiZkw=xgh_vFtE0kK7YxFCnr-h7aeTBnety0g@mail.gmail.com>

Thanks Jonathan!

On Sun, Jan 23, 2022 at 5:51 PM Jonathan Wakely <jwakely@redhat.com> wrote:

> I thought I'd CC'd Maged on this patch, but apparently not. I've
> pushed it to trunk now.
>
> On Fri, 21 Jan 2022 at 13:50, Jonathan Wakely wrote:
> >
> > Tested powerpc64le-linux. Does anybody see a problem with this change?
> >
> >
> > The non-atomic store that sets both reference counts to zero uses a
> > type-punned pointer, which has undefined behaviour. We could use memset
> > to write 8 bytes, but we don't actually need it to be a single store
> > anyway. No other thread can observe the values, that's why it's safe to
> > use non-atomic stores in the first place. So we can just set each count
> > to zero.
> >
> > With -fstore-merging (which is enabled by default at -O2) GCC produces
> > the same code for this as for memset or the type punned store. Clang
> > does that store merging even at -O1.
> >
> > libstdc++-v3/ChangeLog:
> >
> >         * include/bits/shared_ptr_base.h
> (_Sp_counted_base<>::_M_release):
> >         Set members to zero without type punning.
> > ---
> >  libstdc++-v3/include/bits/shared_ptr_base.h | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libstdc++-v3/include/bits/shared_ptr_base.h
> b/libstdc++-v3/include/bits/shared_ptr_base.h
> > index 5b8f84b65be..b2f955b41f7 100644
> > --- a/libstdc++-v3/include/bits/shared_ptr_base.h
> > +++ b/libstdc++-v3/include/bits/shared_ptr_base.h
> > @@ -340,7 +340,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> >               // we are releasing the last strong reference. No other
> >               // threads can observe the effects of this _M_release()
> >               // call (e.g. calling use_count()) without a data race.
> > -             *(long long*)(&_M_use_count) = 0;
> > +             _M_weak_count = _M_use_count = 0;
> >               _GLIBCXX_SYNCHRONIZATION_HAPPENS_AFTER(&_M_use_count);
> >               _GLIBCXX_SYNCHRONIZATION_HAPPENS_AFTER(&_M_weak_count);
> >               _M_dispose();
> > --
> > 2.31.1
> >
>
>

      reply	other threads:[~2022-01-24  4:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 13:49 Jonathan Wakely
2022-01-23 22:51 ` Jonathan Wakely
2022-01-24  4:46   ` Maged Michael [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='CABBFi08J5MTckPu+NaYrcs9AU5C0X5NGdqtQiMw7=noB3jDqxQ@mail.gmail.com' \
    --to=maged.michael@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@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).