From: <rsbecker@nexbridge.com>
To: "'Jeff King'" <peff@peff.net>
Cc: <git@vger.kernel.org>
Subject: RE: [BUG] Git 2.43.0-rc0 - t4216 unpack(Q) invalid type
Date: Fri, 3 Nov 2023 15:18:51 -0400 [thread overview]
Message-ID: <00a801da0e8a$97acc950$c7065bf0$@nexbridge.com> (raw)
In-Reply-To: <20231103162119.GC1470570@coredump.intra.peff.net>
On November 3, 2023 12:21 PM Jeff King wrote:
>On Fri, Nov 03, 2023 at 12:07:17PM -0400, rsbecker@nexbridge.com wrote:
>
>> What I get from Perl is
>> $ perl -e '
>> > my $bytes = "\1\2\3\4\5\6\7\8";
>> > my $q = eval { unpack("Q>", $bytes) };
>> > print "Q = ", defined($q) ? $q : "($@)", "\n";
>> > my ($n1, $n2) = unpack("NN", $bytes);
>> > print "n1 = $n1\n";
>> > print "n2 = $n2\n";
>> > print "computed quad = ", ($n1 << 32) | $n2, "\n"; '
>> Q = (Invalid type 'Q' in unpack at -e line 3.
>> )
>> n1 = 16909060
>> n2 = 84281144
>> computed quad = 84281144
>
>OK, that matches what I expected. Hopefully the patch I just sent (our mails just
>crossed) will fix it for you.
>
>> Because perl itself is 32-bit, not 64-bit on this platform. So even
>> moving git to 64-bit will not correct the issue.
>
>Yep, exactly.
Your patch worked! Thanks.
prev parent reply other threads:[~2023-11-03 19:19 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
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 [this message]
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='00a801da0e8a$97acc950$c7065bf0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).