This is the mail archive of the
mailing list for the glibc project.
Re: 2.26 freeze in a little over a week
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Palmer Dabbelt <palmer at dabbelt dot com>, siddhesh at gotplt dot org
- Cc: nd at arm dot com, Andrew Waterman <andrew at sifive dot com>, Darius Rad <darius at bluespec dot com>, libc-alpha at sourceware dot org, carlos at redhat dot com
- Date: Thu, 22 Jun 2017 18:09:20 +0100
- Subject: Re: 2.26 freeze in a little over a week
- Authentication-results: sourceware.org; auth=none
- Authentication-results: redhat.com; dkim=none (message not signed) header.d=none;redhat.com; dmarc=none action=none header.from=arm.com;
- Nodisclaimer: True
- References: <mhng-6ec60a50-f338-4682-b532-4f4b627b675c@palmer-si-x1c4>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 22/06/17 18:05, Palmer Dabbelt wrote:
> On Thu, 22 Jun 2017 09:49:36 PDT (-0700), email@example.com wrote:
>> PSA: The development freeze for 2.26 is due in a little over a week. 1
>> July is a Saturday, so we have until next week to finish major changes.
>> I have a memcpy implementation for the Qualcomm falkor chip that I hope
>> to post by tomorrow. Are there any major changes that need attention
>> but are not getting it?
> Thanks for the heads up. We're in the process of submitting our RISC-V port,
> do you allow new architecture ports during the freeze? IIRC GCC allowed us to
> submit our port during Stage 4 as it didn't touch any other port's code, and it
> was mentioned that this might be the case for glibc as well.
is the linux kernel abi finalized (upstream in a released version of linux)?
if not then there is a possibility of divergence between kernel and userspace abi.