diff options
| author | Alan Wu <XrXr@users.noreply.github.com> | 2024-02-28 16:21:11 -0500 |
|---|---|---|
| committer | Alan Wu <XrXr@users.noreply.github.com> | 2024-02-28 18:00:22 -0500 |
| commit | f05ad373d84909da7541bd6d6ace38b48eaf24a1 (patch) | |
| tree | e8f6cddf441aefb1ad3074442d9d2f953e00b54e /include | |
| parent | 558b58d330783f663d1cfb37c4af7dc330d490b3 (diff) | |
YJIT: Squash canary before falling back
Recent flaky canary-related CI failures have all happened while trying
to fall back. It's unclear what is leaving the canary on the stack and
causing gen_send_dynamic() to falsely assume that it should be leaf,
and this patch isn't going to help us find the source. One source I
found is Array#<< with a frozen array, but it's unclear if that's what's
causing the CI failures. I'm somewhat afraid to add a canary check to
rb_longjmp() since that might introduce more flaky failures, and maybe
ones unrelated to YJIT.
See: https://github.com/ruby/ruby/actions/runs/8083502532/job/22086714152
See: https://github.com/ruby/ruby/actions/runs/8066858522/job/22035963315
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions