help i stayed up till 5 am reading compiler design papers
31 / ⚧ / code, music, art, games
- they/them/others depending on mood
- echowritescode.dev/
──────────────────────────────
🌸 many-shaped creature
✨ too many projects
🚀 cannot be stopped
🌙 stayed up too late
eggbug enjoyer
──────────────────────────────
header image: chapter 8 complete from celeste
avatar: made using this character builder
📩 email
contact@echowritescode.dev
You must log in to comment.
in reply to @ysaie's post:
Any good ones you’d recommend? For whatever reason I’ve been able to do parsing and VMs but have never been able to grok how to approach a type system so I can have a typed language.
so far i've just been reading about the internals of GCC and Clang, which i don't know that i would recommend as instructional literature since both compilers are such massive projects with varying amounts of ossified bullshit, but it's neat to see how they each have done things in the big picture. GCC for example almost immediately converts its source languages into a generic IR and does type checking on that, but Clang keeps its frontend data structures very close to the source code for a long time, right up until the optimizer takes over.
i did find a slide deck from a lecture about type checking specifically, i'll see if i can find it again...
Pinned Tags