[Bug nptl/17514] Assert failure unlocking ERRORCHECK mutex after timedlock (related to lock elision)

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17514

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  5aded6f2abbe19bc77e563b7db10aa9dd037a90d (commit)
      from  9200e581e500b6c8ad52733f9c0ac3efc8d4b4b9 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5aded6f2abbe19bc77e563b7db10aa9dd037a90d

commit 5aded6f2abbe19bc77e563b7db10aa9dd037a90d
Author: Andreas Schwab <schwab@suse.de>
Date:   Wed Jan 13 16:04:42 2016 +0100

    Don't do lock elision on an error checking mutex (bug 17514)

    Error checking mutexes are not supposed to be subject to lock elision.
    That would defeat the error checking nature of the mutex because lock
    elision doesn't record ownership.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                      |   14 ++++++++-
 nptl/Makefile                  |    2 +-
 nptl/pthread_mutex_timedlock.c |    3 +-
 nptl/tst-mutex-errorcheck.c    |   61 ++++++++++++++++++++++++++++++++++++++++
 4 files changed, 76 insertions(+), 4 deletions(-)
 create mode 100644 nptl/tst-mutex-errorcheck.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.