This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Update on freeze status of glibc 2.18?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Ryan Arnold <rsa at us dot ibm dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Siddhesh Poyarekar <siddhesh at redhat dot com>
- Date: Mon, 10 Jun 2013 19:32:50 -0400
- Subject: Re: Update on freeze status of glibc 2.18?
- References: <51B65DE4 dot 4010107 at redhat dot com> <20130610231903 dot D9C602C09B at topped-with-meat dot com>
On 06/10/2013 07:19 PM, Roland McGrath wrote:
>> The Intel TSX lock elision patches are stuck on consensus
>> for env var usage to tune runtime behaviour.
>
> I haven't joined that (ridiculously long) thread. I don't think we can
> settle on acceptable rules for this stuff in this cycle.
OK, so I've been putting my head in the sand about this
and the more I work on it the more work there is to do :-(
I agree that settling on acceptable rules seems like it will
take longer than we want to delay 2.18. We are after all
making time-boxed releases.
I will assume that you would not be opposed to a configure
switch that turns elision on or off with the default being
elision off, but no questionable env vars to tune behaviour.
I'll still keep working on this, but the freeze will go into
effect probably next Monday.
>> What's the status of the API to get and set default thread attributes?
>
> I think it's only blocked on my final round of review.
> I'll be sure to get to that this week.
Thanks.
Cheers,
Carlos.