From: "Sergio Durigan Junior (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: [review] Use libxxhash for hashing, if present
Date: Tue, 15 Oct 2019 23:25:00 -0000 [thread overview]
Message-ID: <20191015232538.A53E326976@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1571050562000.Icab218388b9f829522ed3977f04301ae6d4fc4ca@gnutoolchain-gerrit.osci.io>
Sergio Durigan Junior has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/39
......................................................................
Patch Set 1: Code-Review+1
(1 comment)
Aside from the minor nit of missing whitespace, this LGTM. Thanks!
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/39/1/gdb/utils.c
File gdb/utils.c:
https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/39/1/gdb/utils.c@3447
PS1, Line 3447: return XXH64(str, len, 0);
Missing whitespace between function name and open parenthesis.
next parent reply other threads:[~2019-10-15 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gerrit.1571050562000.Icab218388b9f829522ed3977f04301ae6d4fc4ca@gnutoolchain-gerrit.osci.io>
2019-10-15 23:25 ` Sergio Durigan Junior (Code Review) [this message]
2019-10-16 13:09 ` Christian Biesinger (Code Review)
2019-10-16 13:09 ` Christian Biesinger (Code Review)
2019-10-21 21:16 ` [review v3] " Luis Machado (Code Review)
2019-10-22 16:02 ` [review v5] " Tom Tromey (Code Review)
2019-10-22 16:47 ` [review v6] " Christian Biesinger (Code Review)
2019-10-22 17:08 ` Tom Tromey (Code Review)
2019-10-22 17:55 ` [pushed] " 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=20191015232538.A53E326976@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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