From: "Christian Biesinger (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: [review] Create a correctly-sized demangled names hashtable
Date: Mon, 18 Nov 2019 23:19:00 -0000 [thread overview]
Message-ID: <20191118231904.A695A2816F@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1574118864000.I1f074d38e1d90af58705ec852f90c84cc034cd2e@gnutoolchain-gerrit.osci.io>
Christian Biesinger has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/686
......................................................................
Patch Set 1:
I guess this patch doesn't *technically* depend on the threading changes; but it will have no benefit without them.
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I1f074d38e1d90af58705ec852f90c84cc034cd2e
Gerrit-Change-Number: 686
Gerrit-PatchSet: 1
Gerrit-Owner: Christian Biesinger <cbiesinger@google.com>
Gerrit-Reviewer: Christian Biesinger <cbiesinger@google.com>
Gerrit-Comment-Date: Mon, 18 Nov 2019 23:19:04 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-11-18 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 23:14 Christian Biesinger (Code Review)
2019-11-18 23:19 ` Christian Biesinger (Code Review) [this message]
2019-11-18 23:24 ` Christian Biesinger (Code Review)
2019-11-20 4:42 ` Simon Marchi (Code Review)
2019-11-20 5:33 ` [review v2] " Christian Biesinger (Code Review)
2019-11-20 5:34 ` Christian Biesinger (Code Review)
2019-11-22 2:51 ` Kevin Buettner (Code Review)
2019-11-22 17:44 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-22 17:44 ` Sourceware to Gerrit sync (Code Review)
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=20191118231904.A695A2816F@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
/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