A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1111 ====================================================================== Reported By: torvald Assigned To: ====================================================================== Project: 1003.1(2013)/Issue7+TC1 Issue ID: 1111 Category: Base Definitions and Headers Type: Clarification Requested Severity: Objection Priority: normal Status: New Name: Torvald Riegel Organization: Red Hat User Reference: Section: pthread_rwlock_rdlock/pthread_rwlock_tryrdlock (XSH, 3 System Interfaces) Page Number: (page or range of pages) Line Number: (Line or range of lines) Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2017-01-04 23:06 UTC Last Modified: 2018-06-14 16:15 UTC ====================================================================== Summary: pthread_rwlock_rdlock requirements if TPS is supported are under-specified, error-prone for users, and inefficient ======================================================================
---------------------------------------------------------------------- (0004042) geoffclare (manager) - 2018-06-14 16:15 http://austingroupbugs.net/view.php?id=1111#c4042 ---------------------------------------------------------------------- On P1707 L55544 and L55548 change: <blockquote>the threads involved in the lock</blockquote> to: <blockquote>the threads that hold or are blocked on the lock</blockquote> On P1707 L55546 and L55550 change: <blockquote>or if writers of higher or equal priority are blocked on the lock</blockquote> to: <blockquote>or if the calling thread does not already hold a read lock and writers of higher or equal priority are blocked on the lock</blockquote> On P1707 L55555 insert a paragraph break before: <blockquote>If the read lock is not acquired,</blockquote> and change it to: <blockquote>Whether the Thread Execution Scheduling option is supported or not, if the read lock is not acquired,</blockquote> Issue History Date Modified Username Field Change ====================================================================== 2017-01-04 23:06 torvald New Issue 2017-01-04 23:06 torvald Name => Torvald Riegel 2017-01-04 23:06 torvald Organization => Red Hat 2017-01-04 23:06 torvald Section => pthread_rwlock_rdlock/pthread_rwlock_tryrdlock (XSH, 3 System Interfaces) 2017-01-04 23:06 torvald Page Number => (page or range of pages) 2017-01-04 23:06 torvald Line Number => (Line or range of lines) 2017-01-05 02:13 bhaible Note Added: 0003528 2017-01-05 10:31 bhaible Issue Monitored: bhaible 2017-01-05 12:00 torvald Note Added: 0003534 2017-01-05 12:15 bhaible Note Added: 0003535 2017-01-05 15:56 shware_systems Note Added: 0003536 2017-01-06 13:21 praiskup Issue Monitored: praiskup 2017-01-06 13:34 praiskup Note Added: 0003538 2017-01-07 09:06 Florian Weimer Issue Monitored: Florian Weimer 2017-01-10 11:48 torvald Note Added: 0003540 2018-06-14 16:15 geoffclare Note Added: 0004042 ======================================================================
