Re: [PATCH 15/32] tools/nolibc: use intmax definitions from compiler

On Tue, Mar 04, 2025 at 12:08:56PM +0100, Thomas Weißschuh wrote: > On Tue, Mar 04, 2025 at 08:37:42AM +0100, Willy Tarreau wrote: > > Hi Thomas, > > > > On Tue, Mar 04, 2025 at 08:10:45AM +0100, Thomas Weißschuh wrote: > > > The printf format checking in the compiler uses the intmax types from >

Re: [PATCH 15/32] tools/nolibc: use intmax definitions from compiler

On Tue, Mar 04, 2025 at 08:37:42AM +0100, Willy Tarreau wrote: > Hi Thomas, > > On Tue, Mar 04, 2025 at 08:10:45AM +0100, Thomas Weißschuh wrote: > > The printf format checking in the compiler uses the intmax types from > > the compiler, not libc. This can lead to compiler errors. > > > > Instead

Re: [PATCH 15/32] tools/nolibc: use intmax definitions from compiler

Hi Thomas, On Tue, Mar 04, 2025 at 08:10:45AM +0100, Thomas Weißschuh wrote: > The printf format checking in the compiler uses the intmax types from > the compiler, not libc. This can lead to compiler errors. > > Instead use the types already provided by the compiler. > > Example issue with clan

[PATCH 15/32] tools/nolibc: use intmax definitions from compiler

The printf format checking in the compiler uses the intmax types from the compiler, not libc. This can lead to compiler errors. Instead use the types already provided by the compiler. Example issue with clang 19 for arm64: nolibc-test.c:30:2: error: format specifies type 'uintmax_t' (aka 'unsign