Ruby

ZJIT: Mark profiled objects when marking ISEQ (#13784)

ZJIT: Name side-exit test cases correctly

ZJIT: Optimize opt_and and opt_or instructions for Fixnum

ZJIT: Profile opt_and and opt_or instructions

[DOC] Tweaks for String#clear

[DOC] Tweaks for String#chop

[DOC] Tweaks for String#chr

[DOC] Tweaks for String#chop

Avoid concurrently overflowing of shape_id

Previously it was possible for two atomic increments of next_shape_id
running concurrently to overflow MAX_SHAPE_ID. For this reason we need
to do the test atomically with the allocation in shape_alloc returning...

Always use atomics to get the shape count

When sharing between threads we need both atomic reads and writes. We
probably didn't need to use this in some cases (where we weren't running
in multi-ractor mode) but I think it's best to be consistent.