All Enclosed are the minutes of this weeks call. regards Andrew ------------------ Minutes of the 15th January 2026 Teleconference Austin-1476 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 16th January 2026
Attendees: Andrew Josey,The Open Group Haelwenn Monnier, The Open Group Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR (partial) Geoff Clare, The Open Group Eric Ackermann, CISPA Eric Blake, Red Hat, The Open Group OR Mark Brown (partial) Mark Ziegast, ShWare Systems * General business We confirmed the calendar for upcoming meetings, the next meeting is January 22nd 2026 Andrew noted that he had attended the IEEE MSC meeting and had mentioned the vacancy for the IEEE Organizational representative. Andrew will take an action to review the IEEE ballot pool to see if we can identify a candidate (the candidate needs to be a technical expert who is an IEEE member). * New Business Bug 1965: Why isn't pthread_equal async-signal safe? https://www.austingroupbugs.net/view.php?id=1965 Accepted as marked, interp required, tc1-2024 tag Marked MT-Safe on linux and on illumos, no information on {Free,Net,Open}BSD and macOS, AIX just recommends to not use == as pthread_t is an opaque type. Interpretation response: The standard states that pthread_equal() need not be async-signal-safe, and conforming applications must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: It is believed that no pthread interfaces were required to be async-signal-safe in the original POSIX.1c threads amendment because the standard allowed implementations to define pthread_t as a structure type. However, now that the standard requires pthread_kill() to be async-signal-safe, any such implementation would need a way to pass a pthread_t structure to pthread_kill() in an async-signal-safe manner and thus would be able to use the same method to pass a pthread_t to pthread_equal(). Notes to the Editor (not part of this interpretation): Add pthread_equal() to the list of async-signal-safe functions. Bug 1966: Current/previous job definition scattered and ambiguous OPEN https://www.austingroupbugs.net/view.php?id=1966 * Next Steps We will start at bug 1966 next time. Bugs to return to, bugs 1949, 1616, 1941. The next call is on Thu 2026-01-22 (WEBEX meeting - general bugs) Apologies in advance: Geoff Clare 2026-01-29 The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup) -------- Andrew Josey The Open Group Austin Group Chair Email: [email protected] <mailto:[email protected]> Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub&listid=2481
