[PATCH v3 3/7] Assume support for __extension__ ({ })
Alejandro Colomar
alx@kernel.org
Tue Nov 11 13:18:50 GMT 2025
Hi Bruno,
On Tue, Nov 11, 2025 at 01:09:24PM +0100, Bruno Haible wrote:
> > - long long
>
> Sounds reasonable. Present in gcc >= 2.95.3 at least.
>
> > - _Bool
>
> Sounds reasonable. Present in gcc >= 3.1 at least.
>
> > - restrict
>
> Beware! Present by default in gcc >= 5.x only.
> Only if spelled as __restrict__, it is present in gcc >= 2.95.3 at least.
Okay, let's forget about restrict. It's not that important. I just
thought it could be easily ignored by compilers, but it's not very
useful itself.
> > - inline
>
> Beware! Only 'static inline' is reasonably portable to C99.
> The semantics of 'extern inline' changed in gcc 4.2 / 4.3 / 4.4.
Hmmmm, C99's extern inline is one I'm very interested in. Would you
mind pointing at the changes in 4.x you're referring to? I'd like to
learn about them.
Even if we can't rely on it now, I'd like to be able to rely on it in
the future (maybe 10 years from now?).
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20251111/e60dc2bc/attachment.sig>
More information about the Libc-alpha
mailing list