From: ludo@gnu.org (Ludovic Courtès)
To: "Jan Šmydke" <jan.smydke@gmail.com>
Cc: 31528-done@debbugs.gnu.org
Subject: bug#31528: patch get-bytevector-n to read more than 4 GB
Date: Mon, 18 Jun 2018 14:05:16 +0200 [thread overview]
Message-ID: <874li0wb9f.fsf@gnu.org> (raw)
In-Reply-To: <CAP01H25sxMX-xRXj6eRj95=MoZDdpuEkM-CNwbze63Y-i6bTdw@mail.gmail.com> ("Jan \=\?utf-8\?Q\?\=C5\=A0mydke\=22's\?\= message of "Sat, 19 May 2018 13:10:15 +0200")
Hello Jan,
Jan Šmydke <jan.smydke@gmail.com> skribis:
> The "count" variable was of "unsigned" type (i.e. 32-bit) so I changed it
> to "size_t" and the problem is solved.
>
> Enclosed is the corresponding patch (using format-patch)
>
> Jan Šmydke
> From 5b72b9d9c3cfa40884594eb1d403ec1d2f477d37 Mon Sep 17 00:00:00 2001
> From: Jan Smydke <jan.smydke@gmail.com>
> Date: Sat, 19 May 2018 12:48:01 +0200
> Subject: [PATCH] get-bytevector-n and get-bytevector-n! can now read more than
> 4 GB: var "count" changed from unsigned to size_t
>
> ---
> libguile/r6rs-ports.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Awesome. I adjusted the commit log to match our conventions and
committed.
Thank you!
Ludo’.
prev parent reply other threads:[~2018-06-18 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 11:10 bug#31528: patch get-bytevector-n to read more than 4 GB Jan Šmydke
2018-06-18 12:05 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874li0wb9f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31528-done@debbugs.gnu.org \
--cc=jan.smydke@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.
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).