(u)intN_bfmt macros use (u)intN0_fmt_base instead of (u)intN_fmt_base

From: Cormac Stephenson <c7s_at_kasku.net>
Date: Sun, 20 Nov 2022 19:52:47 +0000

In src/header/bits-template,

line 22:
#define uint_at_BITS_at__bfmt(s, b) uint_at_BITS_at_0_fmt_base(s, (b), 2)

and line 45:
#define int_at_BITS_at__bfmt(s, b) int_at_BITS_at_0_fmt_base(s, (b), 2)

shouldn't have zeros, since this leads to calling uint640_fmt_generic
with 3 arguments instead of 4, once the macros are expanded, which
causes a compile error when you try and use e.g. uint16_bfmt.
Received on Sun Nov 20 2022 - 20:52:47 CET

This archive was generated by hypermail 2.4.0 : Sun Nov 20 2022 - 20:53:24 CET