Minutes of the 30th March 2023 Teleconference Austin-1303 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 31st March 2023 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Andrew Josey, The Open Group Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. * General news We discussed the IEEE ballot for Draft 3. Andrew is in final stages preparing the review site for the Austin Group (completed after the meeting). Mantis has been updated to add "Draft 3" as a product for bug reporting against Issue 8 drafts. We will start the IEEE ballot on March 31, and it will run for 60 days. Andrew and Nick still have an action to discuss what we need to do to start the ballot at ISO/IEC. Eric B raised another issue related to a C defect. This has been reported in bug 1647, which we discussed later in the meeting. * Carried Forward This section trimmed -- see Austin/1264 Bug 1406: clarification of SEEK_END when current pointer doesn't match buffer size OPEN https://austingroupbugs.net/view.php?id=1406 Actions carried forward: ACTION: Andrew to contact Rich Felker (dalias) and Alan Coopersmith (Solaris) for feedback. Completed ACTION: Eric B to contact glibc folks. Bug 1616: Standardize mktemp utility OPEN https://austingroupbugs.net/view.php?id=1616 We will need a sponsor; it is not suitable for inclusion in Issue 8. ACTION: Eric to ask The Open Group to sponsor adding the mktemp utility (for Issue 9). Bug 1291: Add method to obtain pthread attributes OPEN https://austingroupbugs.net/view.php?id=1291 Needs additional details and sponsor for Issue 9 Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 (brought forward) Don has an action to produce a proposal. Bug 1622: Standardize getpeereid function OPEN https://austingroupbugs.net/view.php?id=1622 Action: Eric B to ask The Open Group if they are willing to sponsor this function for Issue 9. * Current Business Bug 1630: Alias names https://austingroupbugs.net/view.php?id=1630 OPEN (brought forward) There is a proposal in the etherpad for feedback. See https://posix.rhansen.org/p/2023-02-27 Bug 1641: sockaddr_storage is not alias safe Accepted as Marked https://austingroupbugs.net/view.php?id=1641 This item is tagged for Issue 8. On page 386 line 13115 section DESCRIPTION, change: When a pointer to a sockaddr_storage structure is cast as a pointer to a sockaddr structure, the ss_family field of the sockaddr_storage structure shall map onto the sa_family field of the sockaddr structure. When a pointer to a sockaddr_storage structure is cast as a pointer to a protocol-specific address structure, the ss_family field shall map onto a field of that structure that is of type sa_family_t and that identifies the protocol’s address family. to: When a pointer to a sockaddr_storage structure is cast as a pointer to a sockaddr structure, or vice versa, the ss_family field of the sockaddr_storage structure shall map onto the sa_family field of the sockaddr structure. When a pointer to a sockaddr_storage structure is cast as a pointer to a protocol-specific address structure, or vice versa, the ss_family field shall map onto a field of that structure that is of type sa_family_t and that identifies the protocol’s address family. When a pointer to a sockaddr structure is cast as a pointer to a protocol-specific address structure, or vice versa, the sa_family field shall map onto a field of that structure that is of type sa_family_t and that identifies the protocol’s address family. Additionally, the structures shall be defined in such a way that these casts do not cause the compiler to produce diagnostics about aliasing issues when compiling conforming application (xref to XBD section 2.2) source files. On page 390 line 13260 section APPLICATION USAGE, append a sentence: Note that this example only deals with size and alignment; see RATIONALE for additional issues related to these structures. On page 390 line 13291 section , change RATIONALE from "None" to: Note that defining the sockaddr_storage and sockaddr structures using only mechanisms defined in editions of the ISO C standard prior to the 2011 edition (C11) may produce aliasing diagnostics when used in C11 and later editions of the ISO C standard. Because of the large body of existing code utilizing sockets in a way that was well-defined in the 1999 edition of the ISO C standard (C99) but could trigger undefined behavior if C11/C17 aliasing detection were enforced, this standard mandates that casts between pointers to the various socket address structures do not produce aliasing diagnostics, so as to preserve well-defined semantics. An implementation's header files may need to use anonymous unions, or even an implementation-specific extension such as a [[__may_alias__]] attribute, to comply with the requirements of this standard. Bug 1647: printf("%lc", (wint_t)0) can't output NUL byte OPEN https://austingroupbugs.net/view.php?id=1647 The meeting continued discussing this item in detail. A proposal is added to the bug (see bug note 6239) and we will continue on this item next time. Next Steps ---------- The next calls are on: Mon 2023-04-03 (general bugs) Thu 2023-04-06 (general bugs) tentative 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)