CoreMark score and more failed optimizations
Another two weeks or so wrestling with compilers. Not always successful, but numerous lessons were learned in the process, which I’ll take as a (small) win.
On the bright side, there were new releases of RISC-V crates with more improvements, and there is now a CoreMark runner, which allows somewhat objective comparison of interpreter performance against alternatives.
How to not make interpreter faster
I like posting updates with substantial performance improvements, but sometimes that is just not happening despite plausible approaches and substantial effort. It is still a useful learning experience to share, though. And I have non-performance improvements to share too, so let’s get to it.
Major RISC-V improvements
I spent a lot of time working on the RISC-V interpreter in the last few weeks and got some substantial improvements. Performance is largely the same, but there are still many notable changes both for the project and potential external users now that the crates were published on crates.io (spoiler, new versions were published since).