From: Christian Couder <christian.couder@gmail.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git <git@vger.kernel.org>, "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jonathan Tan" <jonathantanmy@google.com>,
"Brandon Williams" <bmwill@google.com>,
"Christian Couder" <chriscool@tuxfamily.org>
Subject: Re: [PATCH 2/3] t: add t0016-oidmap.sh
Date: Sun, 9 Jun 2019 23:51:35 +0200 [thread overview]
Message-ID: <CAP8UFD3iDY8gAm09OK2uQzG6bsB+06wVcGC6pjOgttb4sZ9F+w@mail.gmail.com> (raw)
In-Reply-To: <20190609212130.GC24208@szeder.dev>
On Sun, Jun 9, 2019 at 11:21 PM SZEDER Gábor <szeder.dev@gmail.com> wrote:
>
> On Sun, Jun 09, 2019 at 10:24:55PM +0200, Christian Couder wrote:
> > On Sun, Jun 9, 2019 at 11:23 AM SZEDER Gábor <szeder.dev@gmail.com> wrote:
> > >
> > > New Perl dependencies always make Dscho sad... :)
> >
> > Yeah, I was not sure how to do it properly in shell so I was hoping I
> > would get suggestions about this. Thanks for looking at this!
> >
> > I could have hardcoded the values as it is done in t0011-hashmap.sh,
> > but I thought it was better to find a function that does he job.
>
> Well, I'm fine with hardcoding the expected hash values (in network
> byte order) as well, because then we won't add another git process
> upstream of a pipe that would pop up during audit later...
Ok, I think I will do that then.
> > > So, 'test oidmap' from the previous patch prints the value we want to
> > > check with:
> > >
> > > printf("%u\n", sha1hash(oid.hash));
> >
> > Yeah, I did it this way because "test-hashmap.c" does the same kind of
> > thing to print hashes:
> >
> > printf("%u %u %u %u\n",
> > strhash(p1), memhash(p1, strlen(p1)),
> > strihash(p1), memihash(p1, strlen(p1)));
> >
> > > First, since object ids inherently make more sense as hex values, it
> > > would be more appropriate to print that hash with the '%x' format
> > > specifier,
> >
> > I would be ok with that, but then I think it would make sense to also
> > print hex values in "test-hashmap.c".
> >
> > > and then we wouldn't need Perl's hex() anymore, and thus
> > > could swap the order of the first four bytes in oidmap's hash without
> > > relying on Perl, e.g. with:
> > >
> > > sed -e 's/^\(..\)\(..\)\(..\)\(..\).*/\4\3\2\1/'
> > >
> > > Second, and more importantly, the need for swapping the byte order
> > > indicates that this test would fail on big-endian systems, I'm afraid.
> > > So I think we need an additional bswap32() on the printing side,
> >
> > Ok, but then shouldn't we also use bswap32() in "test-hashmap.c"?
>
> No. The two test scripts/helpers work with different hashes. t0011
> and 'test-hashmap.c' uses the various FNV-1-based hash functions
> (strhash(), memhash(), ...) to calculate an unsigned int hash of the
> items stored in the hashmap, therefore their hashes will be the same
> regardless of endianness.
I see. Thanks for explaining that.
> In an oidmap, however, the hash is simply
> the first four bytes of the object id as an unsigned int as is,
Yeah, I had realized that.
Thanks,
Christian.
next prev parent reply other threads:[~2019-06-09 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 4:49 [PATCH 0/3] Test oidmap Christian Couder
2019-06-09 4:49 ` [PATCH 1/3] t/helper: add test-oidmap.c Christian Couder
2019-06-09 4:49 ` [PATCH 2/3] t: add t0016-oidmap.sh Christian Couder
2019-06-09 9:22 ` SZEDER Gábor
2019-06-09 20:24 ` Christian Couder
2019-06-09 21:21 ` SZEDER Gábor
2019-06-09 21:51 ` Christian Couder [this message]
2019-06-10 16:46 ` Junio C Hamano
2019-06-13 17:19 ` Jeff King
2019-06-13 17:52 ` SZEDER Gábor
2019-06-13 19:02 ` Jeff King
2019-06-13 22:22 ` Junio C Hamano
2019-06-14 10:36 ` Christian Couder
2019-06-09 4:49 ` [PATCH 3/3] oidmap: use sha1hash() instead of static hash() function Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD3iDY8gAm09OK2uQzG6bsB+06wVcGC6pjOgttb4sZ9F+w@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=szeder.dev@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).