Steel Bank Common Lisp 2.3.5 released
1–10 of 32 posts
Re: Steel Bank Common Lisp 2.3.5 released
#2For those who didn't follow, some news from 2022:
- SBCL is now callable as a shared library
- SIMD support
- faster (de)compression with zstd
- TRACE supports tracing macro functions, compiler-macro functions, individual methods and local functions (flet and labels)
- the SBCL repository reached 20,000 commits.
- Prebuilt SBCL binary for Android (Termux) (unofficial)
https://lisp-journey.gitlab.io/blog/these-years-in-common-li...
Re: Steel Bank Common Lisp 2.3.5 released
#3I haven't looked in a while, so I'm wondering what SBCL's GC latency profile is like nowadays. IIRC, it used to be a non-incremental STW conservative GC, which is a bit unfortunate.
Re: Steel Bank Common Lisp 2.3.5 released
#4I haven't looked in a while, so I'm wondering what SBCL's GC latency profile is like nowadays. IIRC, it used to be a non-incremental STW conservative GC, which is a bit unfortunate.
This might align with your interest, from 2023.
Re: Steel Bank Common Lisp 2.3.5 released
#5I haven't looked in a while, so I'm wondering what SBCL's GC latency profile is like nowadays. IIRC, it used to be a non-incremental STW conservative GC, which is a bit unfortunate.
This might align with your interest, from 2023. https://applied-langua.ge/~hayley/swcl-gc.pdf
Thank you!
Re: Steel Bank Common Lisp 2.3.5 released
#6For such a small team developing SBCL, it has been hugely stable, consistent, and advancing for years. SBCL has many ways it could improve, but it definitely exceeds most bars of quality for serious—even commercial—projects.
Re: Steel Bank Common Lisp 2.3.5 released
#7I haven't looked in a while, so I'm wondering what SBCL's GC latency profile is like nowadays. IIRC, it used to be a non-incremental STW conservative GC, which is a bit unfortunate.
It's at least good enough to release a game on Steam. Here's an experience report: https://raw.githubusercontent.com/Shinmera/talks/master/els2... (https://kandria.com/)
> Overall we have needed to do surprisingly little actual performance analysis and optimisation work to make Kandria run well. This is definitely in large part thanks to SBCL’s quite good native code compiler and type inference systems, and the prior work we’ve done to design critical libraries to not be completely obscene in terms of their performance characteristics.
> […]
Re: Steel Bank Common Lisp 2.3.5 released
#8I haven't looked in a while, so I'm wondering what SBCL's GC latency profile is like nowadays. IIRC, it used to be a non-incremental STW conservative GC, which is a bit unfortunate.
Follow-up question: is there a way to "freeze" the GC? As in, I've done all my allocations, now I want to run a main loop uninterrupted, and force clean up inside at_exit().
Re: Steel Bank Common Lisp 2.3.5 released
#9I haven't looked in a while, so I'm wondering what SBCL's GC latency profile is like nowadays. IIRC, it used to be a non-incremental STW conservative GC, which is a bit unfortunate.
Follow-up question: is there a way to "freeze" the GC? As in, I've done all my allocations, now I want to run a main loop uninterrupted, and force clean up inside at_exit().
Try setting or binding SB-KERNEL:*GC-INHIBIT* to true.
Re: Steel Bank Common Lisp 2.3.5 released
#10I haven't looked in a while, so I'm wondering what SBCL's GC latency profile is like nowadays. IIRC, it used to be a non-incremental STW conservative GC, which is a bit unfortunate.
Follow-up question: is there a way to "freeze" the GC? As in, I've done all my allocations, now I want to run a main loop uninterrupted, and force clean up inside at_exit().
I think you'll want without-interrupts for that: https://sbcl.org/sbcl-internals/The-deferral-mechanism.html