-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fixing a Bug in PyPy's Incremental GC | PyPy #113
Comments
Interesting account of GC bug hunting. Thanks for sharing. One question you raised was the use of formal approaches to checking the correctness of GC code. When we built the Transactional Sapphire GC (https://doi.org/10.1145/3226225), we found model checking with SPIN to be very helpful. TS is a fully concurrent GC (no pauses) so has lots of opportunities for getting things wrong. We found model checking with SPIN to be fairly straightforward and gave us confidence in our algorithms, and I’ve used it again to check concurrent algorithms. However, there are things to be borne in mind when using it.
|
@rejones thanks a lot for your comment, Richard! The paper looks interesting, thanks for the reference! |
There’s also a tech report with more about our SPIN modelling on my GitHub. Can’t remember if we mentioned that in the paper |
This has broadened my understanding of PYPY's GC. |
Fixing a Bug in PyPy's Incremental GC | PyPy
https://www.pypy.org/posts/2024/03/fixing-bug-incremental-gc.html
The text was updated successfully, but these errors were encountered: