From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: sigproc.cc: add comment
Date: Sun, 30 Aug 2020 14:41:29 +0200 [thread overview]
Message-ID: <20200830124129.GO3272@calimero.vinschen.de> (raw)
In-Reply-To: <20200829100157.27707-1-kbrown@cornell.edu>
On Aug 29 06:01, Ken Brown via Cygwin-patches wrote:
> ---
> winsup/cygwin/sigproc.cc | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/winsup/cygwin/sigproc.cc b/winsup/cygwin/sigproc.cc
> index 2a9734f00..47352c213 100644
> --- a/winsup/cygwin/sigproc.cc
> +++ b/winsup/cygwin/sigproc.cc
> @@ -44,7 +44,11 @@ char NO_COPY myself_nowait_dummy[1] = {'0'};
>
> #define Static static NO_COPY
>
> -/* All my children info. Avoid expensive constructor ops at DLL startup */
> +/* All my children info. Avoid expensive constructor ops at DLL
> + startup.
> +
> + This class can allocate memory. But there's no need to free it
> + because only one instance of the class is created per process. */
> class child_procs {
> #ifdef __i386__
> static const int _NPROCS = 256;
> --
> 2.28.0
Sure, why not.
Thanks,
Corinna
prev parent reply other threads:[~2020-08-30 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 10:01 Ken Brown
2020-08-30 12:41 ` Corinna Vinschen [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=20200830124129.GO3272@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).