Re: [Manual CSS] Suggested changes

2024-10-25 Thread Paul Eggert
Thanks for the suggestions. I installed the attached patch to , as I think that's what you had in mind. If I'm wrong please let us know.Index: manual.css === RCS file: /web/gnulib/gnuli

Re: relicense module 'eealloc' under LGPLv2+

2024-10-25 Thread Bruno Haible via Gnulib discussion list
Jim Meyering wrote: > Hi Bruno, relicensing like that is fine with me. Thanks! Done: 2024-10-25 Bruno Haible eealloc: Relicense under LGPLv2+. Jim Meyering's approval is in . * modules/eeall

Re: Does anybody use Gnulib's eealloc module?

2024-10-25 Thread Paul Eggert
On 2024-10-25 05:20, Bruno Haible wrote: How could we call this module? 'realloc-ee' sounds too synthetic. How about 'alloc-0-nonnull'? Whatever the module's name is, it should affect malloc too, as there's little point to adjusting realloc without also adjusting malloc. This is needed

Re: relicense module 'eealloc' under LGPLv2+

2024-10-25 Thread Jim Meyering
Hi Bruno, relicensing like that is fine with me.

relicense module 'eealloc' under LGPLv2+

2024-10-25 Thread Bruno Haible via Gnulib discussion list
Hi Jim, The file lib/eealloc.h has a notice "Written by Bruno Haible , 2003, based on prior work by Jim Meyering." Following the considerations from [1], it would be useful to make this module usable under LGPLv2+ license instead of GPLv3+, for use by libraries. Looking at the origical code

Re: Does anybody use Gnulib's eealloc module?

2024-10-25 Thread Bruno Haible via Gnulib discussion list
Hi Paul, Paul Eggert wrote: > Does any package use Gnulib's eealloc module? None, according to codesearch.debian.net. And 'safe-alloc' is used by just 1 package: augeas. > Although it seems to code stolen from Coreutils in 2006 That's probably because the header says: Written by Bruno Haib

Re: [PATCH 6/7] xalloc: port to Cheri, strict C23, realloc null

2024-10-25 Thread Bruno Haible via Gnulib discussion list
Paul Eggert wrote: > @@ -63,9 +67,15 @@ xcharalloc (size_t n) > void * > xrealloc (void *p, size_t s) > { > - void *r = realloc (p, s); > - if (!r && (!p || s)) > + /* Work around realloc glitch by treating a 0 size as if it were 1, > + to avoid undefined behavior in strict C23 platforms,

Re: [PATCH 4/7] ialloc: fix realloc-gnu dependency

2024-10-25 Thread Bruno Haible via Gnulib discussion list
Paul Eggert wrote: > * modules/ialloc (Depends-on): Remove realloc-gnu, > as ialloc.c does not depend on GNU semantics for realloc. But it depends on the fact that realloc() sets errno to ENOMEM when it fails. Therefore it needs a dependency on 'realloc-posix'. 2024-10-25 Bruno Haible

[Manual CSS] Suggested changes

2024-10-25 Thread Thérèse Godefroy
Hello, I'm revising the main stylesheet (/style.css) to fix issues in some manuals, but gnulib/manual.css is also involved. There are 2 problematic things in manual.css: * width: 45em is too narrow for some big tables and [1]. One has to go all the way down to the bottom of the element to fin

Re: [PATCH 6/7] xalloc: port to Cheri, strict C23, realloc null

2024-10-25 Thread Bruno Haible via Gnulib discussion list
Thanks for these changes. We really don't want undefined behaviour in xrealloc. Bruno

Re: [PATCH] tests/test-crc.c: New tests for future optimised implementation.

2024-10-25 Thread Bruno Haible via Gnulib discussion list
Sam Russell wrote: > > Bug: code reads one more word from memory than it should. > > This is a good idea. The nice thing with CRC its that it's pseudo-random so > having the extra trailing randomb bytes helps us catch this but also even > uninitialised memory at the end of the string is going to

Re: [PATCH] crc: New optimised slice-by-8 implementation

2024-10-25 Thread Sam Russell
Sorry for the bump, confirming that I've tested on s390x locally (WSL amd64 with docker-qemu running s390x) root@3d86c908e4f5:/gnulib# ./gnulib-tool --with-tests --test crc ... ## -- ## ## Gnulib tests

Re: [PATCH] tests/test-crc.c: New tests for future optimised implementation.

2024-10-25 Thread Sam Russell
> Bug: code reads one more word from memory than it should. This is a good idea. The nice thing with CRC its that it's pseudo-random so having the extra trailing randomb bytes helps us catch this but also even uninitialised memory at the end of the string is going to make the tests fail if we rea