From: Eric Blake <eblake@redhat.com>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: "Tim Rühsen" <tim.ruehsen@gmx.de>,
"Mats Erik Andersson" <mats.andersson@gisladisker.se>
Subject: Re: restrict - summary
Date: Mon, 24 Feb 2020 13:17:06 -0600 [thread overview]
Message-ID: <0feb5532-5358-ea8f-e20d-804db7d3d454@redhat.com> (raw)
In-Reply-To: <5404770.1kdr2JyrPn@omega>
On 2/22/20 4:51 PM, Bruno Haible wrote:
> Here comes the first part: the 'restrict' in the POSIX function declarations.
>
> Note that the POSIX declarations of posix_spawn and posix_spawnp [1] are
> incorrect: They lack a 'restrict' for the file_actions argument.
>
> [1] https://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_spawn.html
Bug reported to the POSIX folks:
https://www.austingroupbugs.net/view.php?id=1328
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-02-24 19:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 14:44 Possible testing case of snprintf Mats Erik Andersson
2020-02-09 15:24 ` Tim Rühsen
2020-02-10 3:02 ` restrict Bruno Haible
2020-02-10 8:39 ` restrict Jeffrey Walton
2020-02-10 10:11 ` restrict Tim Rühsen
2020-02-16 21:44 ` restrict Paul Eggert
2020-02-16 23:49 ` restrict Bruno Haible
2020-02-17 0:14 ` restrict Bruno Haible
2020-02-17 2:46 ` restrict Paul Eggert
2020-02-17 3:53 ` restrict Bruno Haible
2020-02-17 9:51 ` restrict Tim Rühsen
2020-02-17 21:03 ` restrict Bruno Haible
2020-02-17 18:03 ` restrict Paul Eggert
2020-02-17 20:55 ` restrict Bruno Haible
2020-02-17 22:28 ` restrict Paul Eggert
2020-02-17 21:19 ` restrict - summary Bruno Haible
2020-02-22 22:51 ` Bruno Haible
2020-02-24 19:17 ` Eric Blake [this message]
2020-02-23 12:39 ` Bruno Haible
2020-02-23 13:30 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0feb5532-5358-ea8f-e20d-804db7d3d454@redhat.com \
--to=eblake@redhat.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=mats.andersson@gisladisker.se \
--cc=tim.ruehsen@gmx.de \
/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).