This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v3] aarch64: enforce >=64K guard size
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Florian Weimer <fweimer at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Cc: nd at arm dot com, Carlos O'Donell <carlos at redhat dot com>
- Date: Thu, 11 Jan 2018 15:12:20 +0000
- Subject: Re: [PATCH v3] aarch64: enforce >=64K guard size
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Szabolcs dot Nagy at arm dot com;
- Nodisclaimer: True
- References: <5A54987B.6040305@arm.com> <5A55FD81.6040006@arm.com> <f3320c7e-0b8f-3f77-b70f-69d959e460c3@redhat.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 11/01/18 09:32, Florian Weimer wrote:
> On 01/10/2018 12:48 PM, Szabolcs Nagy wrote:
>> meanwhile this passed a build-many-glibcs.py test
>> is this ok for 2.27 ?
>
> I don't think the GCC patch has been committed yet.
>
> I find it baffling what's going on there. Aren't the ARM maintainers interested in this feature?
>
i don't know all the details on the gcc side,
the original patch was identified to be both suboptimal
and incorrect in some cases, however nobody had the time
to fix it.
however there is a commitment to 64k probe interval by
default so even if gcc-8 only does 4k probing or no
probing by default, i would still want the larger guard
size in glibc (it is also safer with little cost).