From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: rsbecker@nexbridge.com, git@vger.kernel.org
Subject: Re: [PATCH] t: avoid perl's pack/unpack "Q" specifier
Date: Sat, 04 Nov 2023 10:47:30 +0900 [thread overview]
Message-ID: <xmqq5y2ii91p.fsf@gitster.g> (raw)
In-Reply-To: <20231103162019.GB1470570@coredump.intra.peff.net> (Jeff King's message of "Fri, 3 Nov 2023 12:20:19 -0400")
Jeff King <peff@peff.net> writes:
> +# Some platforms' perl builds don't support 64-bit integers, and hence do not
> +# allow packing/unpacking quadwords with "Q". The chunk format uses 64-bit file
> +# offsets to support files of any size, but in practice our test suite will
> +# only use small files. So we can fake it by asking for two 32-bit values and
> +# discarding the first (most significant) one, which is equivalent as long as
> +# it's just zero.
> +sub unpack_quad {
> + my $bytes = shift;
> + my ($n1, $n2) = unpack("NN", $bytes);
> + die "quad value exceeds 32 bits" if $n1;
> + return $n2;
> +};
Is this an unnecessary ';' at the end?
> +sub pack_quad {
> + my $n = shift;
> + my $ret = pack("NN", 0, $n);
> + # double check that our original $n did not exceed the 32-bit limit.
> + # This is presumably impossible on a 32-bit system (which would have
> + # truncated much earlier), but would still alert us on a 64-bit build
> + # of a new test that would fail on a 32-bit build (though we'd
> + # presumably see the die() from unpack_quad() in such a case).
> + die "quad round-trip failed" if unpack_quad($ret) != $n;
> + return $ret;
> +}
Nice. Both sub are done carefully.
> # read until we find table-of-contents entry for chunk;
> # note that we cheat a bit by assuming 4-byte alignment and
> # that no ToC entry will accidentally look like a header.
> #
> # If we don't find the entry, copy() will hit EOF and exit
> # (which should cause the caller to fail the test).
> while (copy(4) ne $chunk) { }
> -my $offset = unpack("Q>", copy(8));
> +my $offset = unpack_quad(copy(8));
>
> # In clear mode, our length will change. So figure out
> # the length by comparing to the offset of the next chunk, and
> @@ -38,11 +62,11 @@ sub copy {
> my $id;
> do {
> $id = copy(4);
> - my $next = unpack("Q>", get(8));
> + my $next = unpack_quad(get(8));
> if (!defined $len) {
> $len = $next - $offset;
> }
> - print pack("Q>", $next - $len + length($bytes));
> + print pack_quad($next - $len + length($bytes));
> } while (unpack("N", $id));
> }
next prev parent reply other threads:[~2023-11-04 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 14:50 [BUG] Git 2.43.0-rc0 - t4216 unpack(Q) invalid type rsbecker
2023-11-03 15:01 ` rsbecker
2023-11-03 15:52 ` Jeff King
2023-11-03 16:01 ` rsbecker
2023-11-03 16:20 ` [PATCH] t: avoid perl's pack/unpack "Q" specifier Jeff King
2023-11-04 1:47 ` Junio C Hamano [this message]
2023-11-04 4:59 ` Jeff King
2023-11-03 16:07 ` [BUG] Git 2.43.0-rc0 - t4216 unpack(Q) invalid type rsbecker
2023-11-03 16:21 ` Jeff King
2023-11-03 19:18 ` rsbecker
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=xmqq5y2ii91p.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.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 NNTP newsgroup(s).