From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: newlib@sourceware.org
Subject: Re: [PATCH 1/1] libc: Added implementations and prototypes for
Date: Wed, 28 Jul 2021 20:51:23 -0600 [thread overview]
Message-ID: <faecff5c-d17f-d361-958a-76ae8bd35e99@SystematicSw.ab.ca> (raw)
In-Reply-To: <YQGmCvpRtXsZn1cO@calimero.vinschen.de>
On 2021-07-28 12:46, Corinna Vinschen wrote:
> On Jul 28 09:25, Brian Inglis wrote:
>> On 2021-07-28 03:11, Corinna Vinschen wrote:
>>> Hi Matt,
>>>
>>> thanks for this v2.
>>>
>>> On Jul 24 10:37, Matt Joyce wrote:
>>>> Added implementations for sig2str() and str2sig() in libc/signal in order
>>>> to improve POSIX compliance. Added function prototypes to sys/signal.h.
>>>> Added Makefile.am entries to build the new file.
>>>> ---
>>>> [...]
>>>> +#if __GNU_VISIBLE
>>>
>>> I think this needs discussion. The sig2str/str2sig API has not been
>>> provided yet by GLibC. Using __GNU_VISIBLE in this context looks wrong.
>>> 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
>>
>> and anticipated release date is 2022 from FAQ
>>
>> https://www.opengroup.org/austin/faq.html
>>
>> Q8. Where is the schedule for draft development?
>>
>> so could use:
>>
>> __POSIX_VISIBLE >= 202202 /* FIXME when POSIX Issue 8 released */
>
> Did you mean 202201? Sounds like a good idea in theory. But consider a
> project actually using this value and then the POSIX release defines the
> value 202207 or so. The project might stop to compile correctly. Along
> these lines, using 202212 for the interim might be the better approach.
> Then again, what if the release occurs in 2023 only?
Best guess of earliest release (V8 exactly 8 years after V7 - spooky!)
Jan too early in year for consensus agreement and release process.
Actual value could be later if defined (if so likely 202209 from history
- couple months after NA vacation period) so will still test true.
--
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 2:51 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
2021-07-29 15:45 ` Corinna Vinschen
2021-07-29 2:51 ` Brian Inglis [this message]
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=faecff5c-d17f-d361-958a-76ae8bd35e99@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).