This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/16657] Lock elision breaks pthread_mutex_detroy
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 06 Mar 2014 16:03:38 +0000
- Subject: [Bug nptl/16657] Lock elision breaks pthread_mutex_detroy
- Auto-submitted: auto-generated
- References: <bug-16657-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16657
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #7 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Rich Felker from comment #6)
> It's certainly not "undefined", It's required to return 0 on success, and
> there are no defined errors for destroy in POSIX, so any error returned
> would need to be implementation-defined or occur only in the case of
> undefined behavior.
I agree. With elision you can't detect the EINVAL or EBUSY cases, therefore
returning 0 when elision is enabled is the best solution.
What do you think Andi?
--
You are receiving this mail because:
You are on the CC list for the bug.