Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Oct 22, 2025

See Commits and Changes for more details.


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

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

Earlopain and others added 8 commits October 22, 2025 14:50
This one has been on my mind for a while now.

Currently, there are only tests against the latest syntax version.

This changes the snapshot structure as follows:
* Snapshots at their current location are tested against all syntax versions
* Snapshots inside a version folder like "3.3" are tested against all versions starting from that version
* Snapshots inside a version folder like "3.3-4.2" are tested against all versions in the given range.

This makes sure that as new syntax is added, older versions still work as expected.
I also added a few tests for now valid syntax that should be invalid in older versions (and the other way around as well)

These tests run really fast. So even though it does 3x the work for these, I am still able to run the whole test suite in just 11 seconds.

ruby/prism@5191b1aa68
Previously, when the output register and the base register are the same
in `out = Lea(Mem(out, disp))`, we did

    out = disp
    out = out + out

Which wasn't the desired `out = out + disp`.

Fixes a SEGV with `--zjit-call-threshold=2` in
`bootstraptest/test_yjit.rb`.
ruby/prism@17a6a19 broke ruby/ruby CI
because some tests are only run against parse.y
This will catch that in the future.

ruby/prism@98e1cd5c04
Find ZJIT options in RUN_OPTS/SPECOPTS and put new ones from the bisection script
there too.
Copy the YJIT simple inliner except for the kwargs bit. It works great!
@pull pull bot locked and limited conversation to collaborators Oct 22, 2025
@pull pull bot added the ⤵️ pull label Oct 22, 2025
@pull pull bot merged commit 6fdcd08 into turkdevops:master Oct 22, 2025
1 check 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.

5 participants