From: Rob Browning <rlb@defaultvalue.org>
To: guile-devel@gnu.org
Subject: [PATCH v2 0/6] A handful of post 3.0.10 fixups
Date: Wed, 3 Jul 2024 12:02:09 -0500 [thread overview]
Message-ID: <20240703170335.1003252-1-rlb@defaultvalue.org> (raw)
I generated this set of patches while trying to track down the Debian
buildd failures. The first four are bug fixes, and the other two are
an optimization and a doc fix.
Proposed for main, and if they're deemed plausible, I'll add any
relevant NEWS updates.
The main change as compared to v2 is to the patch, now "Ensure tests
have guile-procedures.txt" that previously proposed adding it to
BUILT_SOURCES. That wasn't quite right.
Thanks
Rob Browning (6):
Ensure GUILE-VERSION changes propagate to .version and Makefiles
Ensure tests have guile-procedures.txt
test-hashing: support 32-bit
scm_i_utf8_string_hash: don't overrun when len is zero
scm_i_utf8_string_hash: optimize ASCII
define-meta-command: mention effects of a missing category
Makefile.am | 24 +++++-------
configure.ac | 1 +
libguile/Makefile.am | 15 +++++---
libguile/hash.c | 56 +++++++++++++++-------------
module/system/repl/command.scm | 2 +
test-suite/standalone/test-hashing.c | 8 +++-
6 files changed, 59 insertions(+), 47 deletions(-)
--
2.43.0
next reply other threads:[~2024-07-03 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 17:02 Rob Browning [this message]
2024-07-03 17:02 ` [PATCH v2 1/6] Ensure GUILE-VERSION changes propagate to .version and Makefiles Rob Browning
2024-07-03 17:02 ` [PATCH v2 2/6] Ensure tests have guile-procedures.txt Rob Browning
2024-07-03 17:02 ` [PATCH v2 3/6] test-hashing: support 32-bit Rob Browning
2024-07-13 0:32 ` Rob Browning
2024-07-03 17:02 ` [PATCH v2 4/6] scm_i_utf8_string_hash: don't overrun when len is zero Rob Browning
2024-07-03 17:02 ` [PATCH v2 5/6] scm_i_utf8_string_hash: optimize ASCII Rob Browning
2024-07-03 17:02 ` [PATCH v2 6/6] define-meta-command: mention effects of a missing category Rob Browning
2024-07-13 0:32 ` Rob Browning
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=20240703170335.1003252-1-rlb@defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
/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).