disable PTHREAD_MUTEX_ERRORCHECK in release mode #1995
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation:
pthread_mutex_t
locks can do advanced error checking withPTHREAD_MUTEX_ERRORCHECK
, the cost of which was unknown. With #1994 Icould now measure it.
The differences from my local machine (M1 MBP) for uncontended locks
are:
PTHREAD_MUTEX_ERRORCHECK
PTHREAD_MUTEX_ERRORCHECK
!Modification:
Do the extended error checking only in debug mode. Note that we still
precondition
on all pthread return values (which is basically free).Result:
Faster code.