public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Nathaniel Shead <nathanieloshead@gmail.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Add const to hash<coroutine_handle<P>>::operator() [PR109165]
Date: Sat, 18 Mar 2023 09:55:31 +0000	[thread overview]
Message-ID: <CACb0b4m0y+JirN3Hrte1iZVN=swehK78czHJV+A1SMj9aah46Q@mail.gmail.com> (raw)
In-Reply-To: <CACEF2k7=Yg_09OiJ5+UKGJvvX+frOWfrU1+-y7Y_kOMSXbe_iA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2194 bytes --]

On Sat, 18 Mar 2023 at 00:49, Nathaniel Shead wrote:

> On Sat, Mar 18, 2023 at 7:36 AM Jonathan Wakely via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> >
> > Tested x86_64-linux. Pushed to trunk. gcc-12 backport needed too.
> >
> > -- >8 --
> >
> > libstdc++-v3/ChangeLog:
> >
> >         PR libstdc++/109165
> >         * include/std/coroutine (hash<>::operator()): Add const.
> >         * testsuite/18_support/coroutines/hash.cc: New test.
> > ---
> >  libstdc++-v3/include/std/coroutine            |  2 +-
> >  .../testsuite/18_support/coroutines/hash.cc   | 22 +++++++++++++++++++
> >  2 files changed, 23 insertions(+), 1 deletion(-)
> >  create mode 100644 libstdc++-v3/testsuite/18_support/coroutines/hash.cc
> >
> > diff --git a/libstdc++-v3/include/std/coroutine
> b/libstdc++-v3/include/std/coroutine
> > index f6e65566f10..b0ca18949db 100644
> > --- a/libstdc++-v3/include/std/coroutine
> > +++ b/libstdc++-v3/include/std/coroutine
> > @@ -345,7 +345,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> >      struct hash<coroutine_handle<_Promise>>
> >      {
> >        size_t
> > -      operator()(const coroutine_handle<_Promise>& __h) noexcept
> > +      operator()(const coroutine_handle<_Promise>& __h) const noexcept
> >        {
> >         return reinterpret_cast<size_t>(__h.address());
> >        }
> > diff --git a/libstdc++-v3/testsuite/18_support/coroutines/hash.cc
> b/libstdc++-v3/testsuite/18_support/coroutines/hash.cc
> > new file mode 100644
> > index 00000000000..68e5e640477
> > --- /dev/null
> > +++ b/libstdc++-v3/testsuite/18_support/coroutines/hash.cc
> > @@ -0,0 +1,22 @@
> > +// { dg-options "-std=gnu++2a" }
> > +// { dg-do run { target c++2a } }
> > +
> > +#include <coroutine>
> > +#include <testsuite_hooks.h>
> > +
> > +void
> > +test01()
> > +{
> > +  std::hash<std::noop_coroutine_handle> h;
> > +  std::size_t v = h(std::noop_coroutine());
> > +
> > +  const auto& ch = h;
> > +  std::size_t v2 = h(std::noop_coroutine()); // PR libstdc++/109165
>
> Is this supposed to be `std::size_t v2 = ch(...)`?
>
>
Doh! Yes, thanks. Fixed by the attached change.

Tested x86_64-linux, pushed to trunk.

[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1018 bytes --]

commit 9b83d4755a7da02f25788fce14bec949e7045f8f
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Mar 17 11:39:55 2023

    libstdc++: Fix test for hash<coroutine_handle<P>>::operator() [PR109165]
    
    libstdc++-v3/ChangeLog:
    
            PR libstdc++/109165
            * testsuite/18_support/coroutines/hash.cc: Use const object
            in second call.

diff --git a/libstdc++-v3/testsuite/18_support/coroutines/hash.cc b/libstdc++-v3/testsuite/18_support/coroutines/hash.cc
index 68e5e640477..81b68f8246a 100644
--- a/libstdc++-v3/testsuite/18_support/coroutines/hash.cc
+++ b/libstdc++-v3/testsuite/18_support/coroutines/hash.cc
@@ -7,11 +7,12 @@
 void
 test01()
 {
+  auto coro = std::noop_coroutine();
   std::hash<std::noop_coroutine_handle> h;
-  std::size_t v = h(std::noop_coroutine());
+  std::size_t v = h(coro);
 
   const auto& ch = h;
-  std::size_t v2 = h(std::noop_coroutine()); // PR libstdc++/109165
+  std::size_t v2 = ch(coro); // PR libstdc++/109165
 
   VERIFY( v2 == v );
 }

      reply	other threads:[~2023-03-18  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 20:36 Jonathan Wakely
2023-03-18  0:49 ` Nathaniel Shead
2023-03-18  9:55   ` Jonathan Wakely [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='CACb0b4m0y+JirN3Hrte1iZVN=swehK78czHJV+A1SMj9aah46Q@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=nathanieloshead@gmail.com \
    /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).