This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Remove ioperm etc. support for arm
- From: Aaro Koskinen <aaro dot koskinen at iki dot fi>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: Phil Blundell <pb at pbcl dot net>, libc-alpha at sourceware dot org
- Date: Fri, 7 Jun 2019 00:53:12 +0300
- Subject: Re: [PATCH] Remove ioperm etc. support for arm
- References: <87o93lo3y9.fsf@oldenburg2.str.redhat.com> <20190529135135.rt3c5fhhser7fik6@hetzner.pbcl.net> <875zptqrwx.fsf@oldenburg2.str.redhat.com> <20190529141820.5nny64ugrvqyzqgd@hetzner.pbcl.net> <87r28hpb0l.fsf_-_@oldenburg2.str.redhat.com> <20190529184028.GC24195@darkstar.musicnaut.iki.fi> <87ef4hp08c.fsf@oldenburg2.str.redhat.com> <20190529201227.GD24195@darkstar.musicnaut.iki.fi> <87imttnewj.fsf@oldenburg2.str.redhat.com>
Hi,
On Wed, May 29, 2019 at 11:12:44PM +0200, Florian Weimer wrote:
> >> Maybe we used to test ARMv4, and GCC changed under us without us
> >> noticing?
> >
> > Don't know if they have ever changed that, but it would probably make
> > sense to add flags to build-many-glibcs.py to build for the lowest
> > supported arch level.
>
> Indeed.
>
> > ARMv4 is already deprecated in GCC, so probably it's OK to remove this
> > stuff from glibc. Personally I'm concerned about armv4t support as I'm
> > running such systems still with modern glibc.
>
> Interesting. Could you perhaps suggest changes to build-many-glibcs.py
> so that we can build an armv4t target as part of the regular runs?
Just building with -march=armv4t should be enough for a start.
A.