search for: schar_min

...39;ll edit later when 1.3 is released. Hi I've found 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...

...broaden the scope, when I know how to modify .in configuration 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...

..... -Chris > I've found 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 &gt...

> > 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