Update on freeze status of glibc 2.18?

[Andi Kleen]

I appreciate all your efforts in designing this new ABI,
but I don't think it's necessary.

> That certainly seems very reasonable.  Do you have a quick summary (or
> pointer to something) of how the C++11 mutex semantics differ from the
> POSIX mandate for PTHREAD_MUTEX_NORMAL?

AFAIK it doesn't have the deadlock specification bug.

I don't think it makes sense to back them with pthread mutexes at all --
even though that is currently done. The pthread mutexes have a lot
of fast path overhead for checking types etc. that C++ mutexes
could in principle avoid. So a high performance implementation would
not be based on the pthread code.

-Andi