2021-10-06 20:34:16 +00:00
|
|
|
#ifndef YJIT_H
|
|
|
|
|
#define YJIT_H 1
|
2021-03-06 23:46:56 +00:00
|
|
|
//
|
|
|
|
|
// This file contains definitions YJIT exposes to the CRuby codebase
|
|
|
|
|
//
|
|
|
|
|
|
2021-09-08 16:01:39 +00:00
|
|
|
#include "ruby/internal/config.h"
|
|
|
|
|
#include "ruby_assert.h" // for RUBY_DEBUG
|
2021-03-24 22:07:26 +00:00
|
|
|
#include "vm_core.h"
|
2021-03-06 23:46:56 +00:00
|
|
|
#include "method.h"
|
|
|
|
|
|
2021-10-06 20:34:16 +00:00
|
|
|
// YJIT_STATS controls whether to support runtime counters in generated code
|
|
|
|
|
// and in the interpreter.
|
2021-09-08 16:01:39 +00:00
|
|
|
#ifndef YJIT_STATS
|
|
|
|
|
# define YJIT_STATS RUBY_DEBUG
|
2021-03-06 23:46:56 +00:00
|
|
|
#endif
|
|
|
|
|
|
2021-12-28 03:57:04 +00:00
|
|
|
// We generate x86 assembly
|
2021-12-31 11:13:11 +00:00
|
|
|
#if (defined(__x86_64__) && !defined(_WIN32)) || (defined(_WIN32) && defined(_M_AMD64)) // x64 platforms without mingw/msys
|
2021-12-14 00:08:01 +00:00
|
|
|
# define YJIT_SUPPORTED_P 1
|
|
|
|
|
#else
|
|
|
|
|
# define YJIT_SUPPORTED_P 0
|
|
|
|
|
#endif
|
|
|
|
|
|
Rust YJIT
In December 2021, we opened an [issue] to solicit feedback regarding the
porting of the YJIT codebase from C99 to Rust. There were some
reservations, but this project was given the go ahead by Ruby core
developers and Matz. Since then, we have successfully completed the port
of YJIT to Rust.
The new Rust version of YJIT has reached parity with the C version, in
that it passes all the CRuby tests, is able to run all of the YJIT
benchmarks, and performs similarly to the C version (because it works
the same way and largely generates the same machine code). We've even
incorporated some design improvements, such as a more fine-grained
constant invalidation mechanism which we expect will make a big
difference in Ruby on Rails applications.
Because we want to be careful, YJIT is guarded behind a configure
option:
```shell
./configure --enable-yjit # Build YJIT in release mode
./configure --enable-yjit=dev # Build YJIT in dev/debug mode
```
By default, YJIT does not get compiled and cargo/rustc is not required.
If YJIT is built in dev mode, then `cargo` is used to fetch development
dependencies, but when building in release, `cargo` is not required,
only `rustc`. At the moment YJIT requires Rust 1.60.0 or newer.
The YJIT command-line options remain mostly unchanged, and more details
about the build process are documented in `doc/yjit/yjit.md`.
The CI tests have been updated and do not take any more resources than
before.
The development history of the Rust port is available at the following
commit for interested parties:
https://github.com/Shopify/ruby/commit/1fd9573d8b4b65219f1c2407f30a0a60e537f8be
Our hope is that Rust YJIT will be compiled and included as a part of
system packages and compiled binaries of the Ruby 3.2 release. We do not
anticipate any major problems as Rust is well supported on every
platform which YJIT supports, but to make sure that this process works
smoothly, we would like to reach out to those who take care of building
systems packages before the 3.2 release is shipped and resolve any
issues that may come up.
[issue]: https://bugs.ruby-lang.org/issues/18481
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Co-authored-by: Noah Gibbs <the.codefolio.guy@gmail.com>
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
2022-04-19 18:40:21 +00:00
|
|
|
// Is the output binary going to include YJIT?
|
|
|
|
|
#if USE_MJIT && USE_YJIT && YJIT_SUPPORTED_P
|
|
|
|
|
# define YJIT_BUILD 1
|
|
|
|
|
#else
|
|
|
|
|
# define YJIT_BUILD 0
|
|
|
|
|
#endif
|
2021-10-01 11:17:09 +00:00
|
|
|
|
Rust YJIT
In December 2021, we opened an [issue] to solicit feedback regarding the
porting of the YJIT codebase from C99 to Rust. There were some
reservations, but this project was given the go ahead by Ruby core
developers and Matz. Since then, we have successfully completed the port
of YJIT to Rust.
The new Rust version of YJIT has reached parity with the C version, in
that it passes all the CRuby tests, is able to run all of the YJIT
benchmarks, and performs similarly to the C version (because it works
the same way and largely generates the same machine code). We've even
incorporated some design improvements, such as a more fine-grained
constant invalidation mechanism which we expect will make a big
difference in Ruby on Rails applications.
Because we want to be careful, YJIT is guarded behind a configure
option:
```shell
./configure --enable-yjit # Build YJIT in release mode
./configure --enable-yjit=dev # Build YJIT in dev/debug mode
```
By default, YJIT does not get compiled and cargo/rustc is not required.
If YJIT is built in dev mode, then `cargo` is used to fetch development
dependencies, but when building in release, `cargo` is not required,
only `rustc`. At the moment YJIT requires Rust 1.60.0 or newer.
The YJIT command-line options remain mostly unchanged, and more details
about the build process are documented in `doc/yjit/yjit.md`.
The CI tests have been updated and do not take any more resources than
before.
The development history of the Rust port is available at the following
commit for interested parties:
https://github.com/Shopify/ruby/commit/1fd9573d8b4b65219f1c2407f30a0a60e537f8be
Our hope is that Rust YJIT will be compiled and included as a part of
system packages and compiled binaries of the Ruby 3.2 release. We do not
anticipate any major problems as Rust is well supported on every
platform which YJIT supports, but to make sure that this process works
smoothly, we would like to reach out to those who take care of building
systems packages before the 3.2 release is shipped and resolve any
issues that may come up.
[issue]: https://bugs.ruby-lang.org/issues/18481
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Co-authored-by: Noah Gibbs <the.codefolio.guy@gmail.com>
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
2022-04-19 18:40:21 +00:00
|
|
|
#if YJIT_BUILD
|
2021-03-06 23:46:56 +00:00
|
|
|
|
Rust YJIT
In December 2021, we opened an [issue] to solicit feedback regarding the
porting of the YJIT codebase from C99 to Rust. There were some
reservations, but this project was given the go ahead by Ruby core
developers and Matz. Since then, we have successfully completed the port
of YJIT to Rust.
The new Rust version of YJIT has reached parity with the C version, in
that it passes all the CRuby tests, is able to run all of the YJIT
benchmarks, and performs similarly to the C version (because it works
the same way and largely generates the same machine code). We've even
incorporated some design improvements, such as a more fine-grained
constant invalidation mechanism which we expect will make a big
difference in Ruby on Rails applications.
Because we want to be careful, YJIT is guarded behind a configure
option:
```shell
./configure --enable-yjit # Build YJIT in release mode
./configure --enable-yjit=dev # Build YJIT in dev/debug mode
```
By default, YJIT does not get compiled and cargo/rustc is not required.
If YJIT is built in dev mode, then `cargo` is used to fetch development
dependencies, but when building in release, `cargo` is not required,
only `rustc`. At the moment YJIT requires Rust 1.60.0 or newer.
The YJIT command-line options remain mostly unchanged, and more details
about the build process are documented in `doc/yjit/yjit.md`.
The CI tests have been updated and do not take any more resources than
before.
The development history of the Rust port is available at the following
commit for interested parties:
https://github.com/Shopify/ruby/commit/1fd9573d8b4b65219f1c2407f30a0a60e537f8be
Our hope is that Rust YJIT will be compiled and included as a part of
system packages and compiled binaries of the Ruby 3.2 release. We do not
anticipate any major problems as Rust is well supported on every
platform which YJIT supports, but to make sure that this process works
smoothly, we would like to reach out to those who take care of building
systems packages before the 3.2 release is shipped and resolve any
issues that may come up.
[issue]: https://bugs.ruby-lang.org/issues/18481
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Co-authored-by: Noah Gibbs <the.codefolio.guy@gmail.com>
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
2022-04-19 18:40:21 +00:00
|
|
|
// Expose these as declarations since we are building YJIT.
|
2021-10-25 18:53:22 +00:00
|
|
|
bool rb_yjit_enabled_p(void);
|
2021-03-06 23:46:56 +00:00
|
|
|
unsigned rb_yjit_call_threshold(void);
|
2021-03-17 23:07:20 +00:00
|
|
|
void rb_yjit_invalidate_all_method_lookup_assumptions(void);
|
|
|
|
|
void rb_yjit_method_lookup_change(VALUE klass, ID mid);
|
Rust YJIT
In December 2021, we opened an [issue] to solicit feedback regarding the
porting of the YJIT codebase from C99 to Rust. There were some
reservations, but this project was given the go ahead by Ruby core
developers and Matz. Since then, we have successfully completed the port
of YJIT to Rust.
The new Rust version of YJIT has reached parity with the C version, in
that it passes all the CRuby tests, is able to run all of the YJIT
benchmarks, and performs similarly to the C version (because it works
the same way and largely generates the same machine code). We've even
incorporated some design improvements, such as a more fine-grained
constant invalidation mechanism which we expect will make a big
difference in Ruby on Rails applications.
Because we want to be careful, YJIT is guarded behind a configure
option:
```shell
./configure --enable-yjit # Build YJIT in release mode
./configure --enable-yjit=dev # Build YJIT in dev/debug mode
```
By default, YJIT does not get compiled and cargo/rustc is not required.
If YJIT is built in dev mode, then `cargo` is used to fetch development
dependencies, but when building in release, `cargo` is not required,
only `rustc`. At the moment YJIT requires Rust 1.60.0 or newer.
The YJIT command-line options remain mostly unchanged, and more details
about the build process are documented in `doc/yjit/yjit.md`.
The CI tests have been updated and do not take any more resources than
before.
The development history of the Rust port is available at the following
commit for interested parties:
https://github.com/Shopify/ruby/commit/1fd9573d8b4b65219f1c2407f30a0a60e537f8be
Our hope is that Rust YJIT will be compiled and included as a part of
system packages and compiled binaries of the Ruby 3.2 release. We do not
anticipate any major problems as Rust is well supported on every
platform which YJIT supports, but to make sure that this process works
smoothly, we would like to reach out to those who take care of building
systems packages before the 3.2 release is shipped and resolve any
issues that may come up.
[issue]: https://bugs.ruby-lang.org/issues/18481
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Co-authored-by: Noah Gibbs <the.codefolio.guy@gmail.com>
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
2022-04-19 18:40:21 +00:00
|
|
|
void rb_yjit_cme_invalidate(rb_callable_method_entry_t *cme);
|
2021-03-06 23:46:56 +00:00
|
|
|
void rb_yjit_collect_vm_usage_insn(int insn);
|
2021-04-07 19:51:50 +00:00
|
|
|
void rb_yjit_collect_binding_alloc(void);
|
|
|
|
|
void rb_yjit_collect_binding_set(void);
|
2021-07-07 18:15:40 +00:00
|
|
|
bool rb_yjit_compile_iseq(const rb_iseq_t *iseq, rb_execution_context_t *ec);
|
Rust YJIT
In December 2021, we opened an [issue] to solicit feedback regarding the
porting of the YJIT codebase from C99 to Rust. There were some
reservations, but this project was given the go ahead by Ruby core
developers and Matz. Since then, we have successfully completed the port
of YJIT to Rust.
The new Rust version of YJIT has reached parity with the C version, in
that it passes all the CRuby tests, is able to run all of the YJIT
benchmarks, and performs similarly to the C version (because it works
the same way and largely generates the same machine code). We've even
incorporated some design improvements, such as a more fine-grained
constant invalidation mechanism which we expect will make a big
difference in Ruby on Rails applications.
Because we want to be careful, YJIT is guarded behind a configure
option:
```shell
./configure --enable-yjit # Build YJIT in release mode
./configure --enable-yjit=dev # Build YJIT in dev/debug mode
```
By default, YJIT does not get compiled and cargo/rustc is not required.
If YJIT is built in dev mode, then `cargo` is used to fetch development
dependencies, but when building in release, `cargo` is not required,
only `rustc`. At the moment YJIT requires Rust 1.60.0 or newer.
The YJIT command-line options remain mostly unchanged, and more details
about the build process are documented in `doc/yjit/yjit.md`.
The CI tests have been updated and do not take any more resources than
before.
The development history of the Rust port is available at the following
commit for interested parties:
https://github.com/Shopify/ruby/commit/1fd9573d8b4b65219f1c2407f30a0a60e537f8be
Our hope is that Rust YJIT will be compiled and included as a part of
system packages and compiled binaries of the Ruby 3.2 release. We do not
anticipate any major problems as Rust is well supported on every
platform which YJIT supports, but to make sure that this process works
smoothly, we would like to reach out to those who take care of building
systems packages before the 3.2 release is shipped and resolve any
issues that may come up.
[issue]: https://bugs.ruby-lang.org/issues/18481
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Co-authored-by: Noah Gibbs <the.codefolio.guy@gmail.com>
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
2022-04-19 18:40:21 +00:00
|
|
|
void rb_yjit_init(void);
|
|
|
|
|
void rb_yjit_bop_redefined(int redefined_flag, enum ruby_basic_operators bop);
|
|
|
|
|
void rb_yjit_constant_state_changed(ID id);
|
|
|
|
|
void rb_yjit_iseq_mark(void *payload);
|
|
|
|
|
void rb_yjit_iseq_update_references(void *payload);
|
|
|
|
|
void rb_yjit_iseq_free(void *payload);
|
2021-03-06 23:46:56 +00:00
|
|
|
void rb_yjit_before_ractor_spawn(void);
|
2021-12-06 22:09:52 +00:00
|
|
|
void rb_yjit_constant_ic_update(const rb_iseq_t *const iseq, IC ic);
|
2021-10-01 22:38:39 +00:00
|
|
|
void rb_yjit_tracing_invalidate_all(void);
|
2021-03-06 23:46:56 +00:00
|
|
|
|
Rust YJIT
In December 2021, we opened an [issue] to solicit feedback regarding the
porting of the YJIT codebase from C99 to Rust. There were some
reservations, but this project was given the go ahead by Ruby core
developers and Matz. Since then, we have successfully completed the port
of YJIT to Rust.
The new Rust version of YJIT has reached parity with the C version, in
that it passes all the CRuby tests, is able to run all of the YJIT
benchmarks, and performs similarly to the C version (because it works
the same way and largely generates the same machine code). We've even
incorporated some design improvements, such as a more fine-grained
constant invalidation mechanism which we expect will make a big
difference in Ruby on Rails applications.
Because we want to be careful, YJIT is guarded behind a configure
option:
```shell
./configure --enable-yjit # Build YJIT in release mode
./configure --enable-yjit=dev # Build YJIT in dev/debug mode
```
By default, YJIT does not get compiled and cargo/rustc is not required.
If YJIT is built in dev mode, then `cargo` is used to fetch development
dependencies, but when building in release, `cargo` is not required,
only `rustc`. At the moment YJIT requires Rust 1.60.0 or newer.
The YJIT command-line options remain mostly unchanged, and more details
about the build process are documented in `doc/yjit/yjit.md`.
The CI tests have been updated and do not take any more resources than
before.
The development history of the Rust port is available at the following
commit for interested parties:
https://github.com/Shopify/ruby/commit/1fd9573d8b4b65219f1c2407f30a0a60e537f8be
Our hope is that Rust YJIT will be compiled and included as a part of
system packages and compiled binaries of the Ruby 3.2 release. We do not
anticipate any major problems as Rust is well supported on every
platform which YJIT supports, but to make sure that this process works
smoothly, we would like to reach out to those who take care of building
systems packages before the 3.2 release is shipped and resolve any
issues that may come up.
[issue]: https://bugs.ruby-lang.org/issues/18481
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Co-authored-by: Noah Gibbs <the.codefolio.guy@gmail.com>
Co-authored-by: Kevin Newton <kddnewton@gmail.com>
2022-04-19 18:40:21 +00:00
|
|
|
#else
|
|
|
|
|
// !YJIT_BUILD
|
|
|
|
|
// In these builds, YJIT could never be turned on. Provide dummy implementations.
|
|
|
|
|
|
|
|
|
|
static inline bool rb_yjit_enabled_p(void) { return false; }
|
|
|
|
|
static inline unsigned rb_yjit_call_threshold(void) { return UINT_MAX; }
|
|
|
|
|
static inline void rb_yjit_invalidate_all_method_lookup_assumptions(void) {}
|
|
|
|
|
static inline void rb_yjit_method_lookup_change(VALUE klass, ID mid) {}
|
|
|
|
|
static inline void rb_yjit_cme_invalidate(rb_callable_method_entry_t *cme) {}
|
|
|
|
|
static inline void rb_yjit_collect_vm_usage_insn(int insn) {}
|
|
|
|
|
static inline void rb_yjit_collect_binding_alloc(void) {}
|
|
|
|
|
static inline void rb_yjit_collect_binding_set(void) {}
|
|
|
|
|
static inline bool rb_yjit_compile_iseq(const rb_iseq_t *iseq, rb_execution_context_t *ec) { return false; }
|
|
|
|
|
static inline void rb_yjit_init(void) {}
|
|
|
|
|
static inline void rb_yjit_bop_redefined(int redefined_flag, enum ruby_basic_operators bop) {}
|
|
|
|
|
static inline void rb_yjit_constant_state_changed(ID id) {}
|
|
|
|
|
static inline void rb_yjit_iseq_mark(void *payload) {}
|
|
|
|
|
static inline void rb_yjit_iseq_update_references(void *payload) {}
|
|
|
|
|
static inline void rb_yjit_iseq_free(void *payload) {}
|
|
|
|
|
static inline void rb_yjit_before_ractor_spawn(void) {}
|
|
|
|
|
static inline void rb_yjit_constant_ic_update(const rb_iseq_t *const iseq, IC ic) {}
|
|
|
|
|
static inline void rb_yjit_tracing_invalidate_all(void) {}
|
|
|
|
|
|
|
|
|
|
#endif // #if YJIT_BUILD
|
|
|
|
|
|
2021-03-06 23:46:56 +00:00
|
|
|
#endif // #ifndef YJIT_H
|