diff options
| author | Alan Wu <XrXr@users.noreply.github.com> | 2022-10-04 22:48:05 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-04 22:48:05 -0400 |
| commit | 7293bfe1bf8a696bd218a52582e9026e5e638458 (patch) | |
| tree | e45b5f267ce6567c783d1b14e16afb007de40497 /include/ruby/internal/encoding/string.h | |
| parent | 5fc68e1101d38c9ced4d07ef1526467618109de3 (diff) | |
YJIT: add support for calling bmethods (#6489)
* YJIT: fix a parameter name
* YJIT: add support for calling bmethods
This commit adds support for the VM_METHOD_TYPE_BMETHOD method type in
YJIT. You can get these type of methods from facilities like
Kernel#define_singleton_method and Module#define_method.
Even though the body of these methods are blocks, the parameter setup
for them is exactly the same as VM_METHOD_TYPE_ISEQ, so we can reuse
the same logic in gen_send_iseq(). You can see this from how
vm_call_bmethod() eventually calls setup_parameters_complex() with
arg_setup_method.
Bmethods do need their frame environment to be setup differently. We
handle this by allowing callers of gen_send_iseq() to control the iseq,
the frame flag, and the prev_ep. The `prev_ep` goes into the same
location as the block handler would go into in an iseq method frame.
Co-authored-by: John Hawthorn <john@hawthorn.email>
Co-authored-by: John Hawthorn <john@hawthorn.email>
Notes
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
Diffstat (limited to 'include/ruby/internal/encoding/string.h')
0 files changed, 0 insertions, 0 deletions
