Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.std.c Subject: Re: bit-fields of type unsigned long and unsigned long long Date: Wed, 23 Jun 2021 10:22:10 -0700 Organization: None to speak of Lines: 19 Message-ID: <87pmwcwl6l.fsf@nosuchdomain.example.com> References: <8735t9yda4.fsf@nosuchdomain.example.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="28e7cfb7a9d1bfdd32dfeb115dacde84"; logging-data="3132"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18kl4NqdQFAXLpSQ8OW19UA" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:/eD8WQT7hcmjlbcngfoOGjKP2do= sha1:Z62ReFZKpsunZ8FlNFDtWi0UXxI= Xref: csiph.com comp.std.c:6234 Philipp Klaus Krause writes: >> Given that no compiler (to my knowledge - and I'd be very interested in >> counter-examples) actually has extended integer types, that is surely >> not a problem. > > I think they are mostly used in lesser-known compilers targeting > embedded systems; but AFAIK both GCC and clang have a 24-bit extended > integer type when targeting avr, also used as int24_t and uint24_t in > stdint.h. gcc's documentation says "GCC does not support any extended integer types.". I don't see anything about 24-bit integers. [...] -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Philips Healthcare void Void(void) { Void(); } /* The recursive call of the void */