From 65ab2385e36cf6e2753bc0f262a059d5e323e003 Mon Sep 17 00:00:00 2001 From: Takashi Kokubun Date: Tue, 8 Sep 2020 09:22:27 -0700 Subject: [PATCH] Use size_t for MJIT's max_ivar_index iseq_inline_iv_cache_entry's index is also size_t. %"PRIuSIZE" seems to print warnings against st_index_t in some environments. --- mjit_compile.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mjit_compile.c b/mjit_compile.c index 07c8e9b4b3..d58377380e 100644 --- a/mjit_compile.c +++ b/mjit_compile.c @@ -61,7 +61,7 @@ struct compile_status { struct rb_mjit_compile_info *compile_info; bool merge_ivar_guards_p; // If true, merge guards of ivar accesses rb_serial_t ivar_serial; // ic_serial of IVC in is_entries (used only when merge_ivar_guards_p) - st_index_t max_ivar_index; // Max IVC index in is_entries (used only when merge_ivar_guards_p) + size_t max_ivar_index; // Max IVC index in is_entries (used only when merge_ivar_guards_p) // If `inlined_iseqs[pos]` is not NULL, `mjit_compile_body` tries to inline ISeq there. const struct rb_iseq_constant_body **inlined_iseqs; struct inlined_call_context inline_context;