Re: Code freeze for glibc-2.19

[Roland McGrath <roland at hack dot frob dot com>]

I'm very sorry that I let it fester so long and am still far behind on
replying to the issue, but I think the TLS change is still premature.
It's been as it was for so long that I am fairly skeptical that it's a
burning need for 2.19 rather than 2.20 and it's a very hairy and
subtle change whose ramifications might not be immediately obvious.

In particular, I don't think anyone has considered all the issues of
no longer using the canonical malloc path for allocation when a
non-libc malloc implementation is being used.  I strongly suspect the
new status quo will break ASan in some cases, for example.

I'm not going to jump up and down if the strong consensus is against
me.  But I am not at all sanguine about the level of conservatism
exercised with regard to this change.  It's clearly my fault for not
getting more involved earlier, so I don't blame anyone for what
they've already done in my absence.

I'm not yet prepared to discuss the technical issues in detail,
because I need to catch up on the long threads here first.  I will
make strong efforts to get up to speed and summarize my concerns
early next week.


Thanks,
Roland