After 2 attempts to build a JIT for , finally I think I'm on track, the prev 2 were ok and worked but I wasn't happy with the design and flexibility, The 3rd one is quite good but I have to rewrite a big chunk of da code which will take time but I'm happy.

Today I was investigating an issue in the 's compiler (this issue is giving me headache for weeks) I had to figure out why adds a lib as a link target. Thanks to a lad in an IRC channel and magic of cmake I got to this dependency tree.
Oh boy

hey folks, I'm working on the diagnostic system of . What do you think a good trackback/error message should look like? tell me what you think. Examples or even sketches are welcome.

Rt please.

Just finished up a very very basic JIT implementation for . It still needs more work to be done for the JIT in a environment but it is a good start.

The JIT is going to take longer than I initially thought.

Show thread

It's time to tackle the last piece of wiring required for the compiler. The JIT.

After this step I'll have a fully functional compiler that I can expand by adding features on top a minimal foundation.

"What I cannot create,
I do not understand"
-- Richard Feynman

Last night, I compiled the first native binary image (compile source code to a executable binary) with . It is safe to assume that the compiler's wiring is done (still needs some polish).

I started a video series on "How to build a compiler with LLVM and MLIR", I'll share my progress on the compiler on this series.

youtube.com/playlist?list=PLlO

Show older
lxsameer's backyard

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!