From: Mark Geisert <mark@maxrnd.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH v2] Cygwin: Make <sys/cpuset.h> safe for c89 compilations
Date: Tue, 4 Jul 2023 11:41:58 -0700 [thread overview]
Message-ID: <d2d1c436-f3f9-8e67-1645-0a6d29741973@maxrnd.com> (raw)
In-Reply-To: <ZKQy5w2OlDmv/5iF@calimero.vinschen.de>
Corinna Vinschen wrote:
> On Jul 4 16:33, Corinna Vinschen wrote:
>> On Jul 3 17:51, Mark Geisert wrote:
>>> Four modifications to include/sys/cpuset.h:
>>> * Change C++-style comments to C-style also supported by C++
>>> * Change "inline" to "__inline" on code lines
>>> * Add "#include <sys/cdefs.h>" to make sure __inline is defined
>>> * Don't declare loop variables on for-loop init clauses
>>>
>>> Tested by first reproducing the reported issue with home-grown test
>>> programs by compiling with gcc option "-std=c89", then compiling again
>>> using the modified <sys/cpuset.h>. Other "-std=" options tested too.
>>>
>>> Addresses: https://cygwin.com/pipermail/cygwin-patches/2023q3/012308.html
>>> Fixes: 315e5fbd99ec ("Cygwin: Fix type mismatch on sys/cpuset.h")
>>> Signed-off-by: Mark Geisert <mark@maxrnd.com>
>>>
>>> ---
>>> winsup/cygwin/include/sys/cpuset.h | 49 ++++++++++++++++--------------
>>> winsup/cygwin/release/3.4.7 | 3 ++
>>> 2 files changed, 30 insertions(+), 22 deletions(-)
>>
>> Pushed.
>
> FYI, I missed to notice that you added the release message to the
> already existing 3.4.7 release. I moved it into a new file for 3.4.8.
Thank you for cleaning up after my goof on the version.
Cheers & Regards,
..mark
prev parent reply other threads:[~2023-07-04 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 0:51 Mark Geisert
2023-07-04 14:33 ` Corinna Vinschen
2023-07-04 14:55 ` Corinna Vinschen
2023-07-04 18:41 ` Mark Geisert [this message]
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=d2d1c436-f3f9-8e67-1645-0a6d29741973@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-patches@cygwin.com \
/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).