[PATCH v1 00/35] Require GNU C --at least GCC 5 or Clang 4-- in headers
Alejandro Colomar
alx@kernel.org
Sun Nov 9 23:55:05 GMT 2025
Hi H.J.,
On Mon, Nov 10, 2025 at 07:42:51AM +0800, H.J. Lu wrote:
> On Mon, Nov 10, 2025 at 6:36 AM Alejandro Colomar <alx@kernel.org> wrote:
> > On Sun, Nov 09, 2025 at 02:15:59PM -0800, Collin Funk wrote:
> > > Some of these changes are in files shared with Gnulib, which works
> > > perfectly fine with GCC 4. We had someone building with GCC 4.1
> > > recently, so it is still tested [1].
> > >
> > > I would like to avoid dropping old compiler support if possible. Guix
> > > uses GCC 4 for bootstrapping [2]. If Gnulib drops support for it, I
> > > assume it will make their lives harder.
> >
> > Would it be okay to raise the minimum to GCC 4? That would already
> > remove many hundreds of lines of code.
> >
> >
>
> For installed headers, we should keep supporting the old compilers.
By old you mean GCC 1.x? AFAIK, GCC 2.0 is older than me. I don't
think we should keep code such as
#if __GNUC__ >= 2
# define alignof(TYPE) __alignof__ (TYPE)
#else
# define alignof(TYPE) \
((int) &((struct { char dummy1; TYPE dummy2; } *) 0)->dummy2)
#endif
Have a lovely night!
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/20251110/a03ae1e1/attachment.sig>
More information about the Libc-alpha
mailing list