search for: schar_max

...that the min and max values for integral data types, for Interix 3.5 (gcc automatic macro is __INTERIX), are defined in the system header file: '/usr/include/limits.h': --- /usr/include/limits.h --------------------- ... #define SCHAR_MIN (-128) /* min value for a signed char */ #define SCHAR_MAX 127 /* max value for a signed char */ #define UCHAR_MAX 0xff /* max value for a unsigned char */ #if defined(_CHAR_UNSIGNED) || defined(__CHAR_UNSIGNED__) #define CHAR_MIN 0 #define CHAR_MAX UCHAR_MAX #else #define CHAR_MIN SCHAR_MIN /* mim value for a char */ #define CHAR_MAX SCHAR_MAX /* ma...

...tion files. However, I've found that the min and max values for integral data types, for Interix 3.5 are defined in the system header file: '/usr/include/limits.h': --- /usr/include/limits.h --------------------- ... #define SCHAR_MIN (-128) /* min value for a signed char */ #define SCHAR_MAX 127 /* max value for a signed char */ #define UCHAR_MAX 0xff /* max value for a unsigned char */ #if defined(_CHAR_UNSIGNED) || defined(__CHAR_UNSIGNED__) #define CHAR_MIN 0 #define CHAR_MAX UCHAR_MAX #else #define CHAR_MIN SCHAR_MIN /* mim value for a char */ #define CHAR_MAX SCHAR_MAX /* ma...

...integral data types, for Interix > 3.5 (gcc automatic macro is __INTERIX), are defined in the system header > file: '/usr/include/limits.h': > > --- /usr/include/limits.h --------------------- > ... > #define SCHAR_MIN (-128) /* min value for a signed char */ > #define SCHAR_MAX 127 /* max value for a signed char */ > #define UCHAR_MAX 0xff /* max value for a unsigned char */ > > #if defined(_CHAR_UNSIGNED) || defined(__CHAR_UNSIGNED__) > #define CHAR_MIN 0 > #define CHAR_MAX UCHAR_MAX > #else > #define CHAR_MIN SCHAR_MIN /* mim value for a char *...

...0: note: expanded from macro 'EXTRACT' out_t f(struct nouveau_array *a, int i, int j) { \ ^ nouveau_array.c:50:16: error: illegal storage class on function *extract_f = EXTRACT(char, float, SCHAR_MAX); ^ nouveau_array.c:38:3: note: expanded from macro 'EXTRACT' auto out_t f(struct nouveau_array *, int, int); \ ^ nouveau_array.c:50:16: error: expected ';' at end of declaration *extract_f = EXTRAC...

> > Okay, it's just not immediately undefined behaviour. The C model has more > issues because of the problem with how "trap representation" is defined > (which precludes trap representations for unsigned char, two's complement > signed char, etc.). This interpretation is further stressed because C only explicitly ascribes > undefined behaviour to trap

If we compare the "common" subdirectory between nbdkit @ 6b4178d0fdfe ("ci: Temporarily disable perl in MacOS", 2023-02-27) and libnbd @ d05cd8f384a7 ("Version 1.15.11.", 2023-02-28), we find differences. We can categorize these differences along two (orthogonal) axes: - Intentional or unintentional. Intentional differences are for example when one of the libnbd