Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Sep 11, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.3)

Can you help keep this open source service alive? 💖 Please sponsor : )

st0012 and others added 8 commits September 10, 2025 13:18
* Revert "ZJIT: Removed unused self_val from Send"

This reverts commit 13c2f8d.

* Revert "ZJIT: Removed unused self_val from InvokeSuper"

This reverts commit 877b625.

* ZJIT: Rename self_val in dispatching HIRs to recv

* ZJIT: Remove unnecessary constructor param names
When testing we've found that the concurrent_set objects used for
fstrings can grow quite large, and because they reach oldgen quickly end
up not being collected.

This commit is a bit of a hack but aims to improve that by moving the
objects to not be WB_PROTECTED. "Unprotected" objects do not age and
can't become oldgen, so this allows them to be collected in a minor GC.
Addressed some suggestions from clippy that made sense to me.
It's failing more frequently on CI in Ractor tests lately. To make allow
other PRs to land more smoothly, we can skip the assertion for now.
instead of mutating RubyVM::Instructions and letting the order of
`require` impact its behavior.

Now that we have both RubyVM::TraceInstruction and
RubyVM::ZJITInstruction, it feels too much of a tight coupling to rely
on `require` to be ordered properly.
These `#[cfg(feature = "disasm")]` were unnecessary and we can provide
the information like ruby source location regardless of the availability
of capstone.
@pull pull bot locked and limited conversation to collaborators Sep 11, 2025
@pull pull bot added the ⤵️ pull label Sep 11, 2025
@pull pull bot merged commit 8d05669 into turkdevops:master Sep 11, 2025
1 of 3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants