From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH 0/5] SIGCHLD hijacking for Process.wait compatibility with MJIT
Date: Mon, 25 Jun 2018 00:22:15 +0000 [thread overview]
Message-ID: <20180625002220.29490-1-e@80x24.org> (raw)
[ruby-core:87605] [Ruby trunk Bug#14867]
I plan to squash patches 1-3 before committing, and separate out 4 and 5
The following changes since commit 8c8247c6eb554d32fdb03f199df9c14d18bf71dc:
* 2018-06-25 (2018-06-24 22:08:16 +0000)
are available in the Git repository at:
git://80x24.org/ruby.git chld-hijack
for you to fetch changes up to 02cd6168da97d63a0a9e181706ad3c1732328267:
Revert "spec: skip Process wait specs on MJIT" (2018-06-25 00:18:54 +0000)
----------------------------------------------------------------
Eric Wong (5):
hijack SIGCHLD handler for internal use
fix SIGCHLD hijacking race conditions
mjit.c: allow working on platforms without SIGCHLD
Revert "test_process.rb: skip tests for Bug 14867"
Revert "spec: skip Process wait specs on MJIT"
mjit.c | 68 ++++++++++---
process.c | 181 ++++++++++++++++++++++++++-------
signal.c | 56 ++++++----
spec/mspec/lib/mspec/guards/feature.rb | 6 --
spec/ruby/core/process/wait2_spec.rb | 26 +++--
spec/ruby/core/process/wait_spec.rb | 122 +++++++++++-----------
spec/ruby/core/process/waitall_spec.rb | 66 ++++++------
test/ruby/test_process.rb | 3 -
thread.c | 13 +++
vm_core.h | 3 +
10 files changed, 355 insertions(+), 189 deletions(-)
next reply other threads:[~2018-06-25 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 0:22 Eric Wong [this message]
2018-06-25 0:22 ` [PATCH 1/5] hijack SIGCHLD handler for internal use Eric Wong
2018-06-25 0:22 ` [PATCH 2/5] fix SIGCHLD hijacking race conditions Eric Wong
2018-06-25 0:22 ` [PATCH 3/5] mjit.c: allow working on platforms without SIGCHLD Eric Wong
2018-06-25 0:22 ` [PATCH 4/5] Revert "test_process.rb: skip tests for Bug 14867" Eric Wong
2018-06-25 0:22 ` [PATCH 5/5] Revert "spec: skip Process wait specs on MJIT" Eric Wong
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=20180625002220.29490-1-e@80x24.org \
--to=e@80x24.org \
--cc=spew@80x24.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).