From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 1/2] Rename struct ucontext to struct mcontext
Date: Tue, 31 Mar 2015 17:48:00 -0000 [thread overview]
Message-ID: <551ADDF6.1060608@dronecode.org.uk> (raw)
In-Reply-To: <20150330184735.GA12442@calimero.vinschen.de>
On 30/03/2015 19:47, Corinna Vinschen wrote:
> Just for the records what we talked about on IRC:
>
> On Mar 30 18:32, Jon TURNEY wrote:
>> @@ -45,7 +49,7 @@ struct _fpstate
>> __uint32_t padding[24];
>> };
>>
>> -struct ucontext
>> +struct mcontext
>
> __mcontext so as not to pollute the namespace.
>
>> __uint64_t etr;
>> __uint64_t efr;
>> __uint8_t _internal;
>> - __uint64_t oldmask;
>> };
>
> Remove _internal, keep oldmask. As a result, __mcontext is still
> basically equivalent to Linux' mcontext_t. __mcontext can be
> taken from _my_tls.oldmask.
Thanks for your help with this.
You'll have to help me understand what the difference in meaning between
ucontext_t.uc_sigmask and ucontext_t.uc_mcontext.oldmask is.
In the context of _cygtls::call_signal_handler() is _my_tls.oldmask
correct and not this_oldmask?
next prev parent reply other threads:[~2015-03-31 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 15:25 [PATCH] Make EXCEPTION_POINTERS available to signal handlers Jon TURNEY
2015-03-30 10:21 ` Corinna Vinschen
2015-03-30 17:33 ` Jon TURNEY
2015-03-30 17:33 ` [PATCH 1/2] Rename struct ucontext to struct mcontext Jon TURNEY
2015-03-30 18:47 ` Corinna Vinschen
2015-03-31 17:48 ` Jon TURNEY [this message]
2015-03-31 19:03 ` Corinna Vinschen
2015-03-30 17:33 ` [PATCH 2/2] Make CONTEXT available to signal handlers Jon TURNEY
2015-03-30 19:12 ` 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=551ADDF6.1060608@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).