Skip to content

Remove MJIT worker thread#6006

Merged
k0kubun merged 3 commits intoruby:masterfrom
k0kubun:no-mjit-worker
Jun 15, 2022
Merged

Remove MJIT worker thread#6006
k0kubun merged 3 commits intoruby:masterfrom
k0kubun:no-mjit-worker

Conversation

@k0kubun
Copy link
Member

@k0kubun k0kubun commented Jun 11, 2022

[Misc #18830]

@k0kubun k0kubun force-pushed the no-mjit-worker branch 12 times, most recently from b991c95 to 9b0a7a2 Compare June 15, 2022 04:52
@k0kubun k0kubun force-pushed the no-mjit-worker branch 2 times, most recently from c8e3968 to c99b2d6 Compare June 15, 2022 06:35
@k0kubun k0kubun changed the title Kill MJIT worker thread Eliminate MJIT worker thread Jun 15, 2022
@k0kubun k0kubun changed the title Eliminate MJIT worker thread Remove MJIT worker thread Jun 15, 2022
@k0kubun k0kubun marked this pull request as ready for review June 15, 2022 07:54
@k0kubun k0kubun merged commit 1162523 into ruby:master Jun 15, 2022
@k0kubun k0kubun deleted the no-mjit-worker branch June 15, 2022 16:40
k0kubun added a commit that referenced this pull request Jun 15, 2022
k0kubun added a commit to k0kubun/ruby that referenced this pull request Jul 14, 2022
Since ruby#6006, we no longer avoid executing GC on mjit_worker.c and thus
there's no need to carefully change how we write code whether you're in
mjit.c or mjit_worker.c anymore.
k0kubun added a commit that referenced this pull request Jul 15, 2022
Since #6006, we no longer avoid executing GC on mjit_worker.c and thus
there's no need to carefully change how we write code whether you're in
mjit.c or mjit_worker.c anymore.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant