public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Thomas Rodgers <rodgert@appliantology.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
	 Thomas Rodgers <trodgers@redhat.com>
Subject: Re: [PATCH] [libstdc++] Remove unused hasher instance.
Date: Fri, 4 Jun 2021 21:30:15 +0100	[thread overview]
Message-ID: <CACb0b4n7bQLRM-rv8z2t-3_dhaLnz_pzUHa1PRk44eC2tmRoEA@mail.gmail.com> (raw)
In-Reply-To: <20210604195156.706986-1-rodgert@appliantology.com>

On Fri, 4 Jun 2021 at 20:54, Thomas Rodgers wrote:

> This is a remnant of poorly executed refactoring.
>

OK for trunk and gcc-11, thanks.



> libstdc++-v3/ChangeLog:
>
>         * include/std/barrier (__tree_barrier::_M_arrive): Remove
>         unnecessary hasher instantiation.
> ---
>  libstdc++-v3/include/std/barrier | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/libstdc++-v3/include/std/barrier
> b/libstdc++-v3/include/std/barrier
> index fd61fb4f9da..4210e30d1ce 100644
> --- a/libstdc++-v3/include/std/barrier
> +++ b/libstdc++-v3/include/std/barrier
> @@ -103,7 +103,6 @@ It looks different from literature pseudocode for two
> main reasons:
>                            static_cast<__barrier_phase_t>(__old_phase_val
> + 2);
>
>         size_t __current_expected = _M_expected;
> -       std::hash<std::thread::id> __hasher;
>         __current %= ((_M_expected + 1) >> 1);
>
>         for (int __round = 0; ; ++__round)
> --
> 2.26.2
>
>

  reply	other threads:[~2021-06-04 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 19:51 Thomas Rodgers
2021-06-04 20:30 ` Jonathan Wakely [this message]
2021-06-08 23:04   ` Thomas Rodgers

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=CACb0b4n7bQLRM-rv8z2t-3_dhaLnz_pzUHa1PRk44eC2tmRoEA@mail.gmail.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=rodgert@appliantology.com \
    --cc=trodgers@redhat.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).