From bfe5127121a2046fe9d996a64635f6f08d940528 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sat, 5 Jun 2021 07:33:13 -0600 Subject: Configure changes for HAS_NON_INT_BITFIELDS This probe has been available without my realizing it had been merged. Some compilers, chiefly IBM, use only integer-size bitfields, warning when presented with other-sized ones. Allowing other-sized fields is an extension to the C standard. These warnings don't affect the correctness of the code generated, but very many are generated per run, potentially overwhelming the reader into not noticing warnings that are important. --- config_h.SH | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'config_h.SH') diff --git a/config_h.SH b/config_h.SH index 8264f91dce..69103e4195 100755 --- a/config_h.SH +++ b/config_h.SH @@ -2339,6 +2339,13 @@ sed <$CONFIG_H -e 's!^#undef\(.*/\)\*!/\*#define\1 \*!' -e 's!^#un */ #$d_atanh HAS_ATANH /**/ +/* HAS_NON_INT_BITFIELDS: + * This symbol, if defined, indicates that the C compiler accepts, without + * error or warning, struct bitfields that are declared with sizes other + * than plain 'int'; for example 'unsigned char' is accepted. + */ +#$d_non_int_bitfields HAS_NON_INT_BITFIELDS /**/ + /* HAS_BUILTIN_CHOOSE_EXPR: * Can we handle GCC builtin for compile-time ternary-like expressions */ -- cgit v1.2.1