Minutes of the 12th August 2021 Teleconference Austin-1155 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 13th August 2021 Attendees: Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Andrew Josey, The Open Group Geoff Clare, The Open Group Joerg Schilling Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam * General news This was a call dedicated to general bugs. * Outstanding actions (Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 13th June 2019 and earlier) Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR list" OPEN https://austingroupbugs.net/view.php?id=1254 Action: Joerg to investigate how his shell behaves. Bug 713 - Nick to raise with the C committee. This item raised in Austin/1129 and submitted to the C committee in May 2021. * Current Business Bug 1471: Add an orthogonal interface for immediate macro expansion definitions to make Accepted as Marked https://www.austingroupbugs.net/view.php?id=1471 This item is tagged for Issue 8 On page 2888 line 97001 change: macro=value macro::=value to macro=value macro::=value macro:::=value After page 2894 line 97263 add: The following form defines a delayed-expansion macro (replacing any previous definition of the macro named by string1): string1 :::= [string2] by immediately expanding macros in string2, if any, before assigning the value. On page 2895 line 97310, change: The macro $$ shall be replaced by the single character '$'. to: The string "$$" shall be replaced by the single character '$', except during the immediate expansion performed for the :::= operator, where it shall be left unmodified. On page 2910 line 97956, change: Therefore, the standard developers opted to require a new operator "::=" with specific semantics; this operator has semantics closest to the GNU make implementation of ":=", where '$' occurring in the immediate expansion of string2 are not further expanded in subsequent use of the macro, and it was felt that other implementations could easily support the required semantics. to: Therefore, the standard developers opted to require two new operators, "::=" and ":::=", with specific semantics; the "::=" operator has semantics closest to the GNU make implementation of ":=", where '$' occurring in the immediate expansion of string2 are not further expanded in subsequent use of the macro, and the ":::=" operator has semantics closest to the BSD make and smake implementations of ":=", where immediate expansion is performed when assigning to a delayed-expansion macro and "$$" is preserved. It was felt that other implementations could easily support the required semantics. Bug 0374: malloc(0) and realloc(p,0) must not change errno on success Accepted as Marked https://austingroupbugs.net/bug_view_page.php?bug_id=374 Action: Geoff to update the C17 alignment document to incorporate the bug 374 change and post a new version to the C17 bug. This item is tagged for Issue 8 On page 637 line 22010 section calloc(), change: Upon successful completion with both nelem and elsize non-zero, calloc() shall return a pointer to the allocated space. If either nelem or elsize is 0, then either: A null pointer shall be returned [CX]and errno may be set to an implementation-defined value[/CX], or A pointer to the allocated space shall be returned. The application shall ensure that the pointer is not used to access an object. Otherwise, it shall return a null pointer [CX]and set errno to indicate the error[/CX]. to: Upon successful completion, calloc() shall return a pointer to the allocated space; if either nelem or elsize is 0, the application shall ensure that the pointer is not used to access an object. Otherwise, it shall return a null pointer [CX]and set errno to indicate the error[/CX]. On page 637 line 22019 section calloc(), add: The calloc() function may fail if: [EINVAL] nelem or elsize is 0 and the implementation does not support 0 sized allocations. On page 1295 line 43152 section malloc(), change: Upon successful completion with size not equal to 0, malloc() shall return a pointer to the allocated space. If size is 0, then either: A null pointer shall be returned [CX]and errno may be set to an implementation-defined value[/CX], or A pointer to the allocated space shall be returned. The application shall ensure that the pointer is not used to access an object. Otherwise, it shall return a null pointer [CX]and set errno to indicate the error[/CX]. to: Upon successful completion, malloc() shall return a pointer to the allocated space; if size is 0, the application shall ensure that the pointer is not used to access an object. Otherwise, it shall return a null pointer [CX]and set errno to indicate the error[/CX]. On page 1295 line 43161 section malloc(), add: The malloc() function may fail if: [EINVAL] size is 0 and the implementation does not support 0 sized allocations. On page 1788 line 57886 section realloc(), change: A null pointer shall be returned [CX]and, if ptr is not a null pointer, errno shall be set to an implementation-defined value[/CX]. to: A null pointer shall be returned [CX]and, if ptr is not a null pointer, errno shall be set to [EINVAL][/CX]. On page 1788 line 57895 section realloc(), add: The realloc() function may fail if: [EINVAL] size is 0 and the implementation does not support 0 sized allocations. Bug 1436: make: add "-j max_jobs" option to support simultaneous rule processing Accepted as Marked https://austingroupbugs.net/view.php?id=1436 See https://posix.rhansen.org/p/2021-06-10 line 84 This item is tagged for Issue 8. Note this bug is on hold until 1437 resolved. Bug 1437: make: (document .NOTPARALLEL and .WAIT special targets) in RATIONAL OPEN https://austingroupbugs.net/view.php?id=1437 We started on this item and will continue next time. The next call will be a gettext call. The gettext draft in the etherpad is at https://posix.rhansen.org/p/gettext_draft Next Steps ---------- The next calls are on: Mon 2021-08-16 Gettext This call will be for 90 minutes. Thu 2020-08-19 (D2 & general bugs) This call will be 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)