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.
This commit is contained in:
Takashi Kokubun 2020-09-08 09:22:27 -07:00
parent b7d86e330c
commit 65ab2385e3
No known key found for this signature in database
GPG Key ID: 6FFC433B12EE23DD
1 changed files with 1 additions and 1 deletions

View File

@ -61,7 +61,7 @@ struct compile_status {
struct rb_mjit_compile_info *compile_info; struct rb_mjit_compile_info *compile_info;
bool merge_ivar_guards_p; // If true, merge guards of ivar accesses 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) 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. // If `inlined_iseqs[pos]` is not NULL, `mjit_compile_body` tries to inline ISeq there.
const struct rb_iseq_constant_body **inlined_iseqs; const struct rb_iseq_constant_body **inlined_iseqs;
struct inlined_call_context inline_context; struct inlined_call_context inline_context;