ruby.git/gc/mmtk/src/weak_proc.rs, branch v4.0.4 The Ruby Programming Language [ruby/mmtk] Skip weak references that are special consts 2025-07-30T13:26:19+00:00 Peter Zhu peter@peterzhu.ca 2025-07-29T20:50:58+00:00 74887a2c121bef639b7aae8d81d1e758994b5062 If a reference marked weak becomes a special const, it will crash because it is not a GC handled object. We should skip special consts here. https://github.com/ruby/mmtk/commit/870a79426b 
If a reference marked weak becomes a special const, it will crash because
it is not a GC handled object. We should skip special consts here.

https://github.com/ruby/mmtk/commit/870a79426b
[ruby/mmtk] Fix warnings from cargo fmt 2025-07-29T21:45:11+00:00 Peter Zhu peter@peterzhu.ca 2025-07-29T21:05:17+00:00 1a4c0a99138186a0b53174639e9819f33621092f https://github.com/ruby/mmtk/commit/84975a8840 
https://github.com/ruby/mmtk/commit/84975a8840
[ruby/mmtk] Fix clippy warnings 2025-07-29T21:45:10+00:00 Peter Zhu peter@peterzhu.ca 2025-07-29T21:03:00+00:00 f608095b84ed31af87f1e2529f89b8b0517e281a https://github.com/ruby/mmtk/commit/45f991578e 
https://github.com/ruby/mmtk/commit/45f991578e
[ruby/mmtk] Fix clippy warnings and formatting. 2025-05-30T14:55:42+00:00 Kunshan Wang wks1986@gmail.com 2025-05-28T06:28:19+00:00 94688bdc7da3ac82f712d3cdc11859ace3bfa8ac We also enable `#![warn(unsafe_op_in_unsafe_fn)]` in the whole mmtk_ruby crate. https://github.com/ruby/mmtk/commit/8b8025f71a 
We also enable `#![warn(unsafe_op_in_unsafe_fn)]` in the whole mmtk_ruby
crate.

https://github.com/ruby/mmtk/commit/8b8025f71a
Move `object_id` in object fields. 2025-05-08T05:58:05+00:00 Jean Boussier jean.boussier@gmail.com 2025-04-21T07:16:07+00:00 f48e45d1e9c4412d5f3ee49241d0b9359651ce7c And get rid of the `obj_to_id_tbl` It's no longer needed, the `object_id` is now stored inline in the object alongside instance variables. We still need the inverse table in case `_id2ref` is invoked, but we lazily build it by walking the heap if that happens. The `object_id` concern is also no longer a GC implementation concern, but a generic implementation. Co-Authored-By: Matt Valentine-House <matt@eightbitraptor.com> 
And get rid of the `obj_to_id_tbl`

It's no longer needed, the `object_id` is now stored inline
in the object alongside instance variables.

We still need the inverse table in case `_id2ref` is invoked, but
we lazily build it by walking the heap if that happens.

The `object_id` concern is also no longer a GC implementation
concern, but a generic implementation.

Co-Authored-By: Matt Valentine-House <matt@eightbitraptor.com>
[ruby/mmtk] [Feature #20860] Implement Mark-Sweep with MMTK 2024-11-22T09:55:24+00:00 Peter Zhu peter@peterzhu.ca 2024-11-21T20:34:07+00:00 19840dfd718465e3bd7a6cf4cf981944443b2985 This commit implements the mark-sweep algorithm using MMTk and allows customizing the plan using MMTK_PLAN. https://github.com/ruby/mmtk/commit/6fea5e5ffc Co-Authored-By: Matt Valentine-House <matt@eightbitraptor.com> 
This commit implements the mark-sweep algorithm using MMTk and allows
customizing the plan using MMTK_PLAN.

https://github.com/ruby/mmtk/commit/6fea5e5ffc

Co-Authored-By: Matt Valentine-House <matt@eightbitraptor.com>
[ruby/mmtk] [Feature #20860] Implement NoGC with MMTk 2024-11-22T09:55:23+00:00 Peter Zhu peter@peterzhu.ca 2024-11-21T20:33:15+00:00 211aef1bc0f42545897892122da44ed01e066186 This commit only supports initializing MMTk with NoGC and object allocation. https://github.com/ruby/mmtk/commit/39aa10e537 Co-Authored-By: Kunshan Wang <wks1986@gmail.com> 
This commit only supports initializing MMTk with NoGC and object
allocation.

https://github.com/ruby/mmtk/commit/39aa10e537

Co-Authored-By: Kunshan Wang <wks1986@gmail.com>