This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: GNU C LIbrary 2.21 freeze date -- January 9th.
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: "Senkevich, Andrew" <andrew dot senkevich at intel dot com>, GNU C Library <libc-alpha at sourceware dot org>, "Zamyatin, Igor" <igor dot zamyatin at intel dot com>, "Melik-Adamyan, Areg" <areg dot melik-adamyan at intel dot com>
- Date: Wed, 7 Jan 2015 13:11:54 +0000
- Subject: Re: GNU C LIbrary 2.21 freeze date -- January 9th.
- Authentication-results: sourceware.org; auth=none
- References: <54AC3FB0 dot 4040701 at redhat dot com> <D373487E0338A646909492FF43BA8BE329748F8F at CDSMSX102 dot ccr dot corp dot intel dot com> <54AD27E5 dot 5050406 at redhat dot com>
On Wed, 7 Jan 2015, Carlos O'Donell wrote:
> On 01/07/2015 07:04 AM, Senkevich, Andrew wrote:
> > what about to postpone freeze date?
> >
> > Intel has signed new copyright agreement with FSF and currently lawyer from FSF is working on finalization.
> > As I know it must be ready very soon. Now it blocks libmvec patches series.
>
> And now the question you should be expecting from me: How long do you need?
>
> Please remember that glibc operates on time-boxed releases, with the goal
> being to make frequent stable releases for the distributions to consume.
>
> Are all of the libmvec patches in a state that they would be ready to commit
> when the authorization from the FSF arrives?
I was waiting for consensus on the ABI documentation before reviewing the
final patches. Have there been public statements from GCC / LLVM / ICC
maintainers agreeing that the proposed ABI documentation describes how
they intend to interpret the OpenMP pragmas on x86_64? If not, you need
to work on pushing things to consensus in those communities.
--
Joseph S. Myers
joseph@codesourcery.com