This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RFC: requiring GCC >= 4.7 to build glibc
- From: Florian Weimer <fweimer at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Mike Frysinger <vapier at gentoo dot org>, libc-alpha at sourceware dot org
- Date: Thu, 15 Oct 2015 15:25:50 +0200
- Subject: Re: RFC: requiring GCC >= 4.7 to build glibc
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1508201344140 dot 30940 at digraph dot polyomino dot org dot uk> <20150820161822 dot GH21236 at vapier> <alpine dot DEB dot 2 dot 10 dot 1510141630430 dot 20331 at digraph dot polyomino dot org dot uk>
On 10/14/2015 06:33 PM, Joseph Myers wrote:
> Here is a 14-patch series for requiring GCC 4.7 and making consequent
> cleanups. I have't written ChangeLog entries or other write-ups for
> individual patches, or tested the individual patches on their own, or
> done non-x86_64 testing where applicable, or done comparisons of
> installed shared libraries to make sure there aren't unexpected
> changes, but it should be illustrative of what requiring GCC 4.7 would
> enable (which I think is more than most such version increments).
I read through the patches, and they look okay to me.
> None of these changes should have any effects on binutils version
> requirements, as binutils 2.22 supports both AVX2 and ARM TLS
> descriptors (although I think a move to requiring 2.23 makes sense on
> general principles of time-based updates to such requirements).
I can only test GCC 4.7 easily with binutils 2.22. Maybe there are
other distributions which offer a 4.7-on-2.23 configuration, though.
Florian