Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Look, I feel like I'm starting to repeat myself here. I don't know how you are imagining this working out, but consider that something like cranelift clocks in in the tens of megabytes, not kilobytes, and still produces worse code than if you had simply AOT-compiled it, while still not being useful as a a general-purpose replacement for any context you might want to JIT compile something. (I don't have any benchmarks for this, but I'd even wager that C->WASM->cranelift with the best available CPU features has trouble competing against C that is AOT-compiled against baseline features.) To come back to your example of Blend2D: it seems to use JIT not primarily to exploit all available CPU features, but because it can perform a number of specific optimizations on its software rendering pipelines; I hope you agree that this is an extremely niche use case.