From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: libc-alpha@sourceware.org, linux-man@vger.kernel.org
Subject: Re: dup3(2) now specified by POSIX.1-2024
Date: Mon, 21 Apr 2025 13:42:50 -0700 [thread overview]
Message-ID: <87ldrtdz5h.fsf@gmail.com> (raw)
In-Reply-To: <edcoajvvdnxi6e2rwbz2zfhj7lysbrhy4rafkew7wu2e3s36gv@rw2jkot3eqvh>
Alejandro Colomar <alx@kernel.org> writes:
> dup3(2) is now specified by POSIX.1-2024. It should be provided when
> the POSIX feature test macros are used. Are there any POSIX.1-2024
> macros yet, or is there any ongoing work for that?
I started working on conform tests for ISO C23 [1]. It is my goal to
work on updating conform for C23 and then moving to POSIX.1-2024.
That will involve updating the feature macros like __USE_GNU to use new
ones defined under _POSIX_C_SOURCE==202405L || _XOPEN_SOURCE==800.
Collin
[1] https://public-inbox.org/libc-alpha/20250413231200.549774-1-collin.funk1@gmail.com/T/#t
next prev parent reply other threads:[~2025-04-21 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 20:30 dup3(2) now specified by POSIX.1-2024 Alejandro Colomar
2025-04-21 20:42 ` Collin Funk [this message]
2025-04-21 20:54 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldrtdz5h.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=alx@kernel.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox