The ruby rpms
3c1be9f9c2
YJIT was introduced as a new feature in Ruby 3.1.0.[1] However, since the commit[2], the YJIT feature support was disabled as a default[3], and we need to set the `--enable-yjit` to the `configure` script to enable the YJIT support, and as the YJIT source code was ported from C to the Rust source, the `rustc` is required to build it. Note that the `rustc` is not used in the runtime process of the YJIT, because the YJIT does not generate the Rust code.[4] The static library `libyjit.a` built from the ``yjit/src/**/*.rs is linked in the build process to create the `libruby.so.3.2.0`, `miniruby` and `ruby` binary files.[4] In the Ruby 3.2.0, YJIT supports only the x86_64 and the aarch64 CPU environments.[1][5] The YJIT test files are executed in the `make check` if the YJIT is supported by `--enable-yjit`. That is equivalent with that the `test/lib/jit_support.rb#yjit_supported?` is `true`.[6] ``` test/ruby/test_yjit_exit_locations.rb test/ruby/test_yjit.rb ``` Note the Ruby's behavior is the same if the the `ruby`'s command `--yjit` or `--yjit-*` options are not specified. [1] https://www.ruby-lang.org/en/news/2021/12/25/ruby-3-1-0-released/ [2] |
||
|---|---|---|
| .gitignore | ||
| libruby.stp | ||
| macros.ruby | ||
| macros.rubygems | ||
| operating_system.rb | ||
| ruby-2.1.0-always-use-i386.patch | ||
| ruby-2.1.0-custom-rubygems-location.patch | ||
| ruby-2.1.0-Enable-configuration-of-archlibdir.patch | ||
| ruby-2.1.0-Prevent-duplicated-paths-when-empty-version-string-i.patch | ||
| ruby-2.3.0-ruby_version.patch | ||
| ruby-2.7.0-Initialize-ABRT-hook.patch | ||
| ruby-2.7.1-Timeout-the-test_bug_reporter_add-witout-raising-err.patch | ||
| ruby-3.1.0-Don-t-query-RubyVM-FrozenCore-for-class-path.patch | ||
| ruby-exercise.stp | ||
| ruby.rpmlintrc | ||
| ruby.spec | ||
| rubygems.attr | ||
| rubygems.con | ||
| rubygems.prov | ||
| rubygems.req | ||
| sources | ||
| test_abrt.rb | ||
| test_systemtap.rb | ||