This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.19 status?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Allan McRae <allan at archlinux dot org>, libc-alpha <libc-alpha at sourceware dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>, Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>, Roland McGrath <roland at hack dot frob dot com>
- Date: Mon, 03 Feb 2014 22:47:17 -0500
- Subject: Re: glibc 2.19 status?
- Authentication-results: sourceware.org; auth=none
- References: <52E649BF dot 5020400 at archlinux dot org> <20140128205657 dot 16DBA74438 at topped-with-meat dot com> <52E9DEB7 dot 4000709 at redhat dot com> <52E9E84F dot 50907 at redhat dot com> <52EA682D dot 90900 at archlinux dot org> <52F03BEC dot 1020202 at archlinux dot org>
On 02/03/2014 08:01 PM, Allan McRae wrote:
> Update as of 2014-02-04:
>
> Fixed since last report:
> - Patch for BZ #16046 (Static dlopen correction fallout fixes) has
> landed
> - All thread safety docs have landed
>
> Ongoing:
> - PPC64/ELF2 ABI - Patches have been provided to set at 2.17
There were 3 patches posted by Adhemerval.
Roland reviewed the first patch.
I reviewed the second and third patch.
Adhemerval as one of the power machine maintainers can go ahead
and check them in.
> - TLS issues(?) - there have been calls for the changes to be reverted.
What TLS issues are these? Can I help in any way?
Cheers,
Carlos