kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

merge revision(s) dfe21ef7a1: [Backport #17874] [Backport #17876]

Browse source 
Do not block JIT with pending_stale_p

	Because we want to flush pending stale units before unloading units, the
	pending_stale_p check is implemented in this waiting loop.

	However, once all methods are called more than --jit-min-calls,
	mjit_worker_wakeup will not be signaled again. As a result, when
	mjit_recompile is called after that and pending_stale_p becomes true,
	MJIT stops processing methods in the unit queue even if the queue is
	very long and MJIT does nothing, waiting for the signal.

	There should be a better way to handle this, but as a fix to be
	backported to Ruby 3.0, let me make an obvious simple commit here.
	---
	 mjit_worker.c | 2 +-
	 1 file changed, 1 insertion(+), 1 deletion(-)
This commit is contained in:
nagachika 2021-05-22 14:59:05 +09:00
parent 2a70d21484
commit e175917f66
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
mjit_worker.c
View file

@ -1380,7 +1380,7 @@ mjit_worker(void)
// Wait until a unit becomes available
CRITICAL_SECTION_START(3, "in worker dequeue");
while ((pending_stale_p || list_empty(&unit_queue.head) || active_units.length >= mjit_opts.max_cache_size) && !stop_worker_p) {
while ((list_empty(&unit_queue.head) || active_units.length >= mjit_opts.max_cache_size) && !stop_worker_p) {
rb_native_cond_wait(&mjit_worker_wakeup, &mjit_engine_mutex);
verbose(3, "Getting wakeup from client");

2
version.h
View file

@ -12,7 +12,7 @@
# define RUBY_VERSION_MINOR RUBY_API_VERSION_MINOR
#define RUBY_VERSION_TEENY 2
#define RUBY_RELEASE_DATE RUBY_RELEASE_YEAR_STR"-"RUBY_RELEASE_MONTH_STR"-"RUBY_RELEASE_DAY_STR
#define RUBY_PATCHLEVEL 76
#define RUBY_PATCHLEVEL 77
#define RUBY_RELEASE_YEAR 2021
#define RUBY_RELEASE_MONTH 5