A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1143 ====================================================================== Reported By: dstaesse Assigned To: ====================================================================== Project: 1003.1(2016)/Issue7+TC2 Issue ID: 1143 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: New Name: Dimitri Staessens Organization: User Reference: Section: 2.9.5 Page Number: 520 Line Number: 18219-18223 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2017-06-14 13:59 UTC Last Modified: 2017-06-20 09:59 UTC ====================================================================== Summary: cancellation points: contradiction between base definition and rationale ======================================================================
---------------------------------------------------------------------- (0003792) terekhov (reporter) - 2017-06-20 09:59 http://austingroupbugs.net/view.php?id=1143#c3792 ---------------------------------------------------------------------- I kinda like the clarification requested many years ago: https://standards.ieee.org/findstds/interps/1003-1c-95_int/pasc-1003.1c-10.html http://people.exeter.ac.uk/DCannon/WG15/mail/wg151111.txt "A cancellation point will also occur in the following functions if the function causes the thread to block:" and note that the old response: "The "intent" is that the functions listed in ISO/IEC 9945-1: 1996 following line 56 in 18.1.2 are allowed to be cancellation points, just in case they are implemented using other routines specified to be cancellation points. Were it not for this language, these routines cannot use routines which are cancellation points in their implementation because the standard says that no POSIX routines other than those specified are cancellation points." does not take into account pthread_setcancelstate() as implementation detail to disable and afterwards restore cancel state. Issue History Date Modified Username Field Change ====================================================================== 2017-06-14 13:59 dstaesse New Issue 2017-06-14 13:59 dstaesse Name => Dimitri Staessens 2017-06-14 13:59 dstaesse Section => 2.9.5 2017-06-14 13:59 dstaesse Page Number => 520 2017-06-14 13:59 dstaesse Line Number => 18219-18223 2017-06-14 14:25 terekhov Note Added: 0003760 2017-06-15 18:49 dstaesse Note Added: 0003765 2017-06-17 12:17 dstaesse Note Added: 0003783 2017-06-19 09:04 terekhov Note Added: 0003784 2017-06-20 03:50 dstaesse Note Added: 0003790 2017-06-20 09:59 terekhov Note Added: 0003792 ======================================================================
