From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: newlib@sourceware.org
Subject: Re: [PATCH 1/1] libc: Added implementations and prototypes for
Date: Thu, 29 Jul 2021 09:29:55 -0600 [thread overview]
Message-ID: <c4f062db-cd37-540d-8608-a87937a238b3@SystematicSw.ab.ca> (raw)
In-Reply-To: <YQJzhOzwcIXb8NDU@calimero.vinschen.de>
On 2021-07-29 03:23, Corinna Vinschen wrote:
> On Jul 28 15:13, Joel Sherrill wrote:
>> On Wed, Jul 28, 2021, 2:54 PM C Howland wrote:
>>>> On Wed, Jul 28, 2021 at 1:46 PM Corinna Vinschen wrote:
>>>>> On Jul 28 09:25, Brian Inglis wrote:
>>>>>> On 2021-07-28 03:11, Corinna Vinschen wrote:
>>>>>>> On Jul 24 10:37, Matt Joyce wrote:
>>>>>>>> +#if __GNU_VISIBLE
>>>>>>> What we need, in fact, is a __POSIX_VISIBLE guard, but
>>>>>>> here's the problem: As far as I can see, the Issue 8
>>>>>>> draft does not yet define a version number.
>>>>>>> If anybody has better information or a good idea how to
>>>>>>> guard this new API in the meantime, I'm all ears.
>>>>>> Current values are:
>>>>>>
>>>>>> __POSIX_VISIBLE 199009
>>>>>> __POSIX_VISIBLE 199209
>>>>>> __POSIX_VISIBLE 199309
>>>>>> __POSIX_VISIBLE 199506
>>>>>> __POSIX_VISIBLE 200112
>>>>>> __POSIX_VISIBLE 200809
>>>>>> __POSIX_VISIBLE 201402
>
> Where did you find the latter one? Per the Open Group docs
> https://pubs.opengroup.org/onlinepubs/9699919799/ the latest valid value
> for _POSIX_C_SOURCE is still 200809, even with POSIX.1-2017.
Searched all installed include files for all __POSIX_VISIBLE date
expressions [Paste As Quotation avoids wrapping commands and output]:
> $ grep '__POSIX_VISIBLE.*[12][90][0-9][0-9][01][0-9]' /usr/{,*86*/sys-root/*/}include/**/*.h
To answer your question:
> $ grep '__POSIX_VISIBLE.*2014' /usr/{,*86*/sys-root/*/}include/**/*.h
> /usr/include/pthread.h:#if __XSI_VISIBLE >= 500 || __POSIX_VISIBLE >= 200112 || __cplusplus >= 201402L
I used sed to extract and standardize so I could sort -u to get the
list, which I saved and added a few comments to:
> /* POSIX-version-dates.h - POSIX dates found in headers and related standards */
>
> #define __POSIX_VISIBLE 199009 /* Issue 1 */
> #define __POSIX_VISIBLE 199209 /* Issue 2 */
> #define __POSIX_VISIBLE 199309 /* Issue 3 UNIX 93 */
> #define __POSIX_VISIBLE 199506 /* Issue 4 SUS V1 UNIX 95 XPG4 COSE Spec 1170 */
> #define __POSIX_VISIBLE 200112 /* Issue 5 SUS V3 UNIX 03 */
> #define __POSIX_VISIBLE 200809 /* Issue 6 SUS V4 */
> #define __POSIX_VISIBLE 201402 /* Issue 7 SUS V4 TC1 UNIX V7 */
> #define __POSIX_VISIBLE 202202? /* Issue 8 SUS V5? UNIX V8? */
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-07-29 15:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 8:37 [PATCH 0/1] V2 Implementation of sig2str/str2sig Matt Joyce
2021-07-24 8:37 ` [PATCH 1/1] libc: Added implementations and prototypes for Matt Joyce
2021-07-28 9:11 ` Corinna Vinschen
2021-07-28 15:25 ` Brian Inglis
2021-07-28 18:46 ` Corinna Vinschen
2021-07-28 19:42 ` Joel Sherrill
[not found] ` <DM3P110MB0522CE441CAB289B69DE18B49AEA9@DM3P110MB0522.NAMP110.PROD.OUTLOOK.COM>
2021-07-28 19:54 ` Fw: " C Howland
2021-07-28 20:13 ` Joel Sherrill
2021-07-29 9:23 ` Corinna Vinschen
2021-07-29 14:45 ` Eric Blake
2021-07-29 15:29 ` Brian Inglis
2021-07-29 15:29 ` Brian Inglis [this message]
2021-07-29 15:45 ` Corinna Vinschen
2021-07-29 2:51 ` Brian Inglis
2021-07-28 18:40 ` Corinna Vinschen
2021-07-29 4:59 ` Matthew Joyce
2021-07-29 9:27 ` Corinna Vinschen
2021-07-29 14:41 ` Eric Blake
-- strict thread matches above, loose matches on Subject: below --
2021-07-17 10:10 [PATCH 0/1] Implementation of sig2str/str2sig Matt Joyce
2021-07-17 10:10 ` [PATCH 1/1] libc: Added implementations and prototypes for Matt Joyce
2021-07-19 9:47 ` Corinna Vinschen
2021-07-19 13:19 ` Joel Sherrill
2021-07-19 14:31 ` Corinna Vinschen
2021-07-20 5:11 ` Matthew Joyce
2021-07-22 5:14 ` Matthew Joyce
2021-07-22 7:55 ` Corinna Vinschen
2021-07-23 5:44 ` Matthew Joyce
2021-07-28 8:44 ` Corinna Vinschen
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=c4f062db-cd37-540d-8608-a87937a238b3@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=newlib@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).