Re: totalorder*: Fix test failures on PA-RISC and MIPS CPUs

2023-10-16 Thread Adhemerval Zanella Netto
On 14/10/23 15:55, Bruno Haible wrote: > On Linux/mips (all 3 ABIs) and on Linux/hppa (configuring a testdir in such > a way that the configuration ignores the totalorder* functions provided by > glibc and instead uses the gnulib replacement instead: > gl_cv_func_totalorder_in_libm=no gl_cv_fu

Re: optimizing totalorder

2023-10-16 Thread Adhemerval Zanella Netto
On 15/10/23 11:59, Bruno Haible wrote: > With the new benchmark in place, I measured the run time of > - the glibc 2.35 implementation of totalorder, > - the gnulib implementation (picked by configuring with > gl_cv_func_totalorder_in_libm=no gl_cv_func_totalorder_no_libm=no \ >

Re: fnmatch: Overcome wchar_t limitations

2023-07-25 Thread Adhemerval Zanella Netto
On 24/07/23 21:46, Bruno Haible wrote: > This patch fixes the remaining problems of fnmatch() on Cygwin, > native Windows, and AIX in 32-bit mode. > > I think the code changes are in glibc style, because > - they use upper-case names for macros, > - the macro names are aligned to the type a

Re: doc: Clarify list of platforms for year2038 support

2023-04-12 Thread Adhemerval Zanella Netto
On 11/04/23 18:58, Paul Eggert wrote: > On 4/11/23 06:45, Adhemerval Zanella Netto wrote: > >> It makes difference on all ABIs with has originally 32 bit time_t support: >> i686, microblaze, arm, m68k, sh, csky, nios2, and hppa, powerpc32, sparc32, >> s390, and

Re: doc: Clarify list of platforms for year2038 support

2023-04-11 Thread Adhemerval Zanella Netto
On 11/04/23 02:33, Paul Eggert wrote: > Oh, I forgot to send comments that partly explain my recent changes in this > area. Here they are, belatedly: > > > On 2023-04-10 05:56, Bruno Haible wrote: > >> +@item >> +Linux/riscv32, > > says this platform used 6