diff options
| author | Karl Williamson <khw@cpan.org> | 2021-06-05 07:33:13 -0600 |
|---|---|---|
| committer | Karl Williamson <khw@cpan.org> | 2021-06-12 09:20:14 -0600 |
| commit | bfe5127121a2046fe9d996a64635f6f08d940528 (patch) | |
| tree | f624010676384b5484c0191c47b1cd430928b05b /uconfig.h | |
| parent | 19c4b24fc62a1e8dd1f7dcaaf337d0eb11dbb6b0 (diff) | |
| download | perl-bfe5127121a2046fe9d996a64635f6f08d940528.tar.gz | |
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.
Diffstat (limited to 'uconfig.h')
| -rw-r--r-- | uconfig.h | 11 |
1 files changed, 9 insertions, 2 deletions
@@ -2304,6 +2304,13 @@ */ /*#define 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. + */ +#define HAS_NON_INT_BITFIELDS /**/ + /* HAS_BUILTIN_CHOOSE_EXPR: * Can we handle GCC builtin for compile-time ternary-like expressions */ @@ -5282,6 +5289,6 @@ #endif /* Generated from: - * 6edd641b187b02d0daa8cb53f5d22f2dcca115a0d3e744f51b0292d2db484ca5 config_h.SH - * a0fa823df68d3b6a854579e3727e8d354614ad995d17f68b691399261825c2d3 uconfig.sh + * dac70e6e1bbb594cb13128b2271cfd83bc32d4cb1d14179edc6100597299d0bf config_h.SH + * bad73e58d466bfe6befab92731c4d075d5d439b45fd11c20585b3514865093a8 uconfig.sh * ex: set ro: */ |