| commit | 88b44ec5fb2ef9a25518be0260156c8a57e14f09 | |
| author | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | |
| Fri, 19 May 2017 10:54:47 +0000 (19 12:54 +0200) | ||
| committer | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | |
| Fri, 19 May 2017 11:16:12 +0000 (19 13:16 +0200) | ||
| tree | 07e5be4898a13caedea5a81eca6e7fa41ed16ac1 | treesnapshot (tar.gz zip) |
| parent | e7a977abea38ffbe855e1fa6e8ac01f71a0f7f2c | commitdiff |
fix definition of __SCHAR_MAX__ & friends
The predefined macros __SCHAR_MAX__, __SHRT_MAX__, __WCHAR_MAX__ &
__CHAR_BIT__ are defined based on the size of these types on
the machine where sparse was compiled.
But since sparse has flags like -m32/-m64 and it's not unlikely
to have one day a flag like -march=<some arch>, better to use
the used by sparse for these types as stored in 'bits_in_char',
'bits_in_short', ...
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
The predefined macros __SCHAR_MAX__, __SHRT_MAX__, __WCHAR_MAX__ &
__CHAR_BIT__ are defined based on the size of these types on
the machine where sparse was compiled.
But since sparse has flags like -m32/-m64 and it's not unlikely
to have one day a flag like -march=<some arch>, better to use
the used by sparse for these types as stored in 'bits_in_char',
'bits_in_short', ...
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
| lib.c | diffblobblamehistory |