These are the draft minutes from yesterday's call. Andrew will need
to allocate the Austin-xxxx document number and add the file to the
document register after he returns.
Regards,
Geoff.
----------------------------------------------
Minutes of the 25th August 2022 Teleconference Austin-xxxx Page 1 of 1
Submitted by Geoff Clare, The Open Group. 26th August 2022
Attendees:
Don Cragun, IEEE PASC OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Mark Ziegast, SHware Systems Dev.
Eric Ackermann, HPI, University of Potsdam
Geoff Clare, The Open Group
Eric Blake, Red Hat, The Open Group OR
Apologies
Andrew Josey, The Open Group
Tom Thompson, IEEE
* General news
This was a call dedicated to general bugs.
As a reminder we agreed previously that there will be NO meetings
on 2022-08-29, 2022-09-05 (due to holidays in the UK and US
respectively)
* Current Business
Bug 1122: POSIX should include gettext() and friends OPEN
and https://posix.rhansen.org/p/gettext_draft
Also https://austingroupbugs.net/file_download.php?file_id=64&type=bug
Geoff's addition to XRAT appendix E and cancellation points lists have been
noted to date.
A new PDF will be needed, but we will continue to wait for more comments first.
To be discussed again when more comments are raised.
Bug 1560: clarify wording of command substitution
https://austingroupbugs.net/view.php?id=1560
Leave this and related bugs 1561 and 1564 open awaiting reviews/discussion.
Bug 1273: glob()'s GLOB_ERR/errfunc and non-directory files OPEN
https://austingroupbugs.net/view.php?id=1273
We will leave this open awaiting feedback.
Bug 768: add "fd-private" POSIX locks to spec OPEN
https://austingroupbugs.net/view.php?id=768
Linux has now had OFD locks for several years, and more code in the
wild is starting to use it - so we have existing practice (see note
2508)
https://www.gnu.org/software/libc/manual/html_mono/libc.html#Open-File-Description-Locks
Starting point of resolution at https://posix.rhansen.org/p/bug768
AI to EricB - take the GNU documentation and turn it into a desired action
Bug 739: CX requirements for strftime seem to conflict with ISO C OPEN
https://austingroupbugs.net/view.php?id=739
Nick completed his action to liaise with the C committee on this
issue. C23 is about to go to ballot, so the way to raise the issue
would be as a ballot comment. This could be done either as a UK or
US national body comment.
Andrew confirmed with the UK C Panel that we can submit comments.
Bug 728: Restrictions on signal handlers are both excessive and insufficient
OPEN
https://austingroupbugs.net/view.php?id=728
The alignment with C17 changes the requirements in this area. There
is still no allowance for accessing const objects or string literals,
so that is something we could consider adding as an extension to
C. Or we could raise the issue with the C committee if we want to
stay in sync with the C standard. Suggestion: raise it as a C23
ballot comment. Depending on the answer, we could implement what
they plan to do, or diverge (or leave things as they are).
AI Nick and Geoff: File ballot comments on C23 (through the US and/or UK
national bodies to WG14).
Bug 708: Make mblen, mbtowc, and wctomb thread-safe for alignment with C11 OPEN
https://austingroupbugs.net/view.php?id=708
This was discussed with WG14:
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm#dr_498
DR 498 (URL above) seems to have an agreed wording change from April
2017, but it has not been applied.
Nick asked the WG14 convenor what happened to that DR.
It appears the item was discussed but in the end the C committee could
not agree an acceptable change, and no alternate proposal was available.
We will need to accept the C wording for now.
Bug 700: Clarify strtoul's behaviour on strings representing negative numbers
OPEN
https://austingroupbugs.net/view.php?id=700
AI: Nick and Geoff to work together on a C23 ballot comment (against N3047
7.24.1.7 para 5).
Bug 689: Possibly unintended allowance for stdio deadlock OPEN
https://austingroupbugs.net/view.php?id=689
Change needs to be coordinated with C23.
AI: Nick and Geoff to work together on a C23 ballot comment (against N3047
7.23.3 para 3).
Bug 618: require isatty and friends to set errno on failure OPEN
https://austingroupbugs.net/view.php?id=618
Action item to EricB: email to various lists to collect results for
sample program (see bug 503 comment 1005 for starting point) for
current errno behavior on various OS
Bug 613: Relationship of automatic object lifetimes to cancellation cleanup
functions is not specified Accepted as Marked
https://austingroupbugs.net/view.php?id=613
This item is tagged for TC3-2008.
After 2018 edition page 48 line 1520 section 3 Definitions, add a new
definition:
3.xxx Code Block
In the context of the System Interfaces Volume of this standard, a
block as defined in the ISO C standard.
After 2018 edition page 1605 line 52316 section pthread_cleanup_pop(), add a
new paragraph:
Invoking a cancellation cleanup handler may terminate the execution
of any code block being executed by the thread whose execution began
after the corresponding invocation of pthread_cleanup_push().
Bug 610: Possible race condition in requirements of exit and their interaction
with threads Accepted as Marked
https://austingroupbugs.net/view.php?id=610
This item is tagged for TC3-2008.
On 2018 edition page 796 line 27070, change:
The exit() function shall then flush all open streams with unwritten
buffered data and close all open streams. Finally, the process shall
be terminated [CX]with the same consequences as described in [xref
to Consequences of Process Termination][/CX].
to:
The exit() function shall then flush all open streams with unwritten
buffered data. [CX]For each stream which is the active handle to its
underlying file descriptor, and for which the file is not already
at EOF and is capable of seeking, the file offset of the underlying
open file description shall be set to the file position of the
stream. For each open stream, the exit() function shall perform the
equivalent of a close() on the file descriptor that is associated
with the stream.[/CX] Finally, the process shall be terminated
[CX]with the same consequences as described in [xref to Consequences
of Process Termination][/CX].
Next Steps
----------
The next calls are on:
No call Mon 2022-08-29
Thu 2022-09-01 (general bugs)
No call Mon 2022-09-05
Thu 2022-09-08 (general bugs)
Apologies in advance:
None.
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)
--
Geoff Clare <g.cl...@opengroup.org>
The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
