ruby.git/ractor_core.h, branch v3_4_9

`Ractor.set_if_absent(key)`

2024-12-12T21:22:13+00:00

to initialize ractor local storage in thread-safety.
[Feature #20875]

define rb_current_ec_set in all cases

2024-11-25T13:05:23+00:00

support `require` in non-main Ractors

2024-11-08T09:02:46+00:00

Many libraries should be loaded on the main ractor because of
setting constants with unshareable objects and so on.

This patch allows to call `requore` on non-main Ractors by
asking the main ractor to call `require` on it. The calling ractor
waits for the result of `require` from the main ractor.

If the `require` call failed with some reasons, an exception
objects will be deliverred from the main ractor to the calling ractor
if it is copy-able.

Same on `require_relative` and `require` by `autoload`.

Now `Ractor.new{pp obj}` works well (the first call of `pp` requires
`pp` library implicitly).

[Feature #20627]

Move responsibility of heap walking into Ruby

2024-09-03T14:05:38+00:00

This commit removes the need for the GC implementation to implement heap
walking and instead Ruby will implement it.

[Feature #20470] Split GC into gc_impl.c

2024-07-03T13:03:40+00:00

This commit splits gc.c into two files:

- gc.c now only contains code not specific to Ruby GC. This includes
  code to mark objects (which the GC implementation may choose not to
  use) and wrappers for internal APIs that the implementation may need
  to use (e.g. locking the VM).

- gc_impl.c now contains the implementation of Ruby's GC. This includes
  marking, sweeping, compaction, and statistics. Most importantly,
  gc_impl.c only uses public APIs in Ruby and a limited set of functions
  exposed in gc.c. This allows us to build gc_impl.c independently of
  Ruby and plug Ruby's GC into itself.

Revert "allow enabling Prism via flag or env var"

2023-12-06T01:21:12+00:00

This reverts commit 9b76c7fc89460ed8e9be40e4037c1d68395c0f6d.

allow enabling Prism via flag or env var

2023-12-05T17:17:14+00:00

Enable Prism using either --prism

    ruby --prism test.rb

or via env var

    RUBY_PRISM=1 ruby test.rb

M:N thread scheduler for Ractors

2023-10-12T05:47:01+00:00

This patch introduce M:N thread scheduler for Ractor system.

In general, M:N thread scheduler employs N native threads (OS threads)
to manage M user-level threads (Ruby threads in this case).
On the Ruby interpreter, 1 native thread is provided for 1 Ractor
and all Ruby threads are managed by the native thread.

From Ruby 1.9, the interpreter uses 1:1 thread scheduler which means
1 Ruby thread has 1 native thread. M:N scheduler change this strategy.

Because of compatibility issue (and stableness issue of the implementation)
main Ractor doesn't use M:N scheduler on default. On the other words,
threads on the main Ractor will be managed with 1:1 thread scheduler.

There are additional settings by environment variables:

`RUBY_MN_THREADS=1` enables M:N thread scheduler on the main ractor.
Note that non-main ractors use the M:N scheduler without this
configuration. With this configuration, single ractor applications
run threads on M:1 thread scheduler (green threads, user-level threads).

`RUBY_MAX_CPU=n` specifies maximum number of native threads for
M:N scheduler (default: 8).

This patch will be reverted soon if non-easy issues are found.

[Bug #19842]

macos: symbols for `rb_execution_context_t` should be internal

2023-07-08T02:31:17+00:00

Remove dependancy of vm_core.h on shape.h

2023-04-06T10:07:16+00:00

so that now shape can happily include gc.h