pselect: Disable signature check on AIX.

On AIX there is the following warning in a testdir of all modules: test-pselect.c:23:18: warning: initialization of 'int (*)(int, fd_set * restrict, fd_set * restrict, fd_set * restrict, const struct timespec * restrict, const sigset_t * restrict)' from incompatible pointer type 'i

Re: vasnprintf: Consider the grouping rule

Collin Funk wrote: > Just curious, do you do a libunistring release roughly around each new > Unicode standard release? Each major Unicode standard release, yes. For minor Unicode standard updates, it depends. > >> And copy nl_langinfo (THOUSEP) into stackbuf? And use the unistring > >> equivelen

Re: vasnprintf: Consider the grouping rule

Bruno Haible writes: > Thanks a lot for this report! Without you, I would not have noticed, > possibly not even before the next libunistring release. Glad to help. Just curious, do you do a libunistring release roughly around each new Unicode standard release? >> And copy nl_langinfo (THOUSEP)

[PATCH 2/2] doc: update some GCC version comments

GCC 15.1 is released, and we can update some commentary now. --- doc/gnulib.texi| 2 +- lib/diffseq.h | 2 +- m4/gnulib-common.m4| 7 +-- tests/test-sprintf-posix.h | 3 ++- 4 files changed, 9 insertions(+), 5 deletions(-) diff --git a/doc/gnulib.texi b/doc/gn

[PATCH 1/2] stddef-h: port better to future GCC 13.4, 14.3

* m4/stddef_h.m4 (gl_STDDEF_H): The idempotency bug should be fixed in GCC 13.4 and 14.3, if and when they’re published. --- ChangeLog | 6 ++ doc/posix-headers/stddef.texi | 2 +- lib/stddef.in.h | 2 +- m4/stddef_h.m4| 8 +--- 4 files cha

Re: vasnprintf: Consider the grouping rule

Hi Collin, > Bruno Haible via Gnulib discussion list writes: > > > This patch fixes it, by considering the 'grouping' sequence of numbers. > > On FreeBSD 15.0 (cfarm427) I see the following warnings: > > In file included from unistdio/u16-u16-vasnprintf.c:57: > ./vasnprintf.c:5224:77:

Re: MinGW-w64 fenv changes.

Bruno Haible writes: > When working on the floating-point code, one needs to have the hardware > specification handy. In this case, it is the > Intel® 64 and IA-32 Architectures Software Developer’s Manual > Combined Volumes: 1, 2A, 2B, 2C, 2D, 3A, 3B, 3C, 3D and 4 > (4700 pages) > > Then,

Re: Rust build system

On Fri, Apr 25, 2025 at 8:51 AM Nikolaos Chatzikonstantinou wrote: > > On Fri, Apr 25, 2025 at 6:33 AM Bruno Haible wrote: > > > > Nikolaos Chatzikonstantinou wrote: > > > > One problem I see with Rust is that currently it does not integrate well > > > > with the GNU Build system, in particular w

Re: Rust build system

On Fri, Apr 25, 2025 at 6:33 AM Bruno Haible wrote: > > Nikolaos Chatzikonstantinou wrote: > > > One problem I see with Rust is that currently it does not integrate well > > > with the GNU Build system, in particular with VPATH builds (see [3] for > > > an example integration). Any improvements on

Re: Rust build system

On Fri, Apr 25, 2025 at 7:28 AM Bruno Haible wrote: > > Jeffrey Walton wrote: > > Also see Rust's Platform Support, > > . Tier 1 > > is expected to build and run correctly. Tier 1 is i686, x86_64 and > > some aarch64. Everything else, Tie

Re: Rust build system

Jeffrey Walton wrote: > Also see Rust's Platform Support, > . Tier 1 > is expected to build and run correctly. Tier 1 is i686, x86_64 and > some aarch64. Everything else, Tiers 2 & 3, are a best effort with no > guarantees. The web page t

Re: Rust build system

On Fri, Apr 25, 2025 at 6:34 AM Bruno Haible via Gnulib discussion list wrote: > > Nikolaos Chatzikonstantinou wrote: > > > One problem I see with Rust is that currently it does not integrate well > > > with the GNU Build system, in particular with VPATH builds (see [3] for > > > an example integr

Re: MinGW-w64 fenv changes.

Hi Collin, > I can look at porting it but I have no knowledge of x86 floating point, Thanks for volunteering to handle this. When working on the floating-point code, one needs to have the hardware specification handy. In this case, it is the Intel® 64 and IA-32 Architectures Software Developer

Re: Rust build system

Nikolaos Chatzikonstantinou wrote: > > One problem I see with Rust is that currently it does not integrate well > > with the GNU Build system, in particular with VPATH builds (see [3] for > > an example integration). Any improvements on that front would be welcome. > > > > [3] > > https://git.sava