Skip to content

Fix load catch table write barrier #13669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jhawthorn
Copy link
Member

I tried fixing this in 521b2fc, but re-running wbcheck with the stricter WBCHECK_VERIFY_AFTER_WB, revealed that this write barrier was fired too early, before the object was actually written to the parent.

This solves the issue by writing the table to the parent immediately (and using calloc so that we don't mark random garbage).

@ruby ruby deleted a comment from Pricer187 Jun 20, 2025
@jhawthorn jhawthorn force-pushed the wbcheck_catch_take_take_2 branch from 61f9843 to 685e874 Compare June 20, 2025 06:13
I tried fixing this in 521b2fc, but
re-running wbcheck with the stricter WBCHECK_VERIFY_AFTER_WB, revealed
that this write barrier was fired too early, before the object was
actually written to the parent.

This solves the issue by writing the table to the parent immediately
(and using calloc so that we don't mark random garbage).
@jhawthorn jhawthorn force-pushed the wbcheck_catch_take_take_2 branch from 685e874 to 1a8705c Compare June 20, 2025 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant