Calypsi is a collection of compilers and assemblers, which can be used to generate code for various retro platforms under Windows, Linux and macOS. Now version 5.15 has been released:
Calypsi is a collection of compilers and assemblers, which can be used to generate code for various retro platforms under Windows, Linux and macOS. Now version 5.15 has been released:
Nice article on Brainfuck compiler optimization. Makes me remember when I wrote a BF interpreter in high school for my Texas Instruments Voyage 200.
http://calmerthanyouare.org/2015/01/07/optimizing-brainfuck.html
Surely i can't be the only person who thinks that -O1/2/3 are somehow lacking as #compiler flags? We need -Osmall! And -OMGTEHFASTERERER! And variations on both! And combinations of variations!
Rewriting the symbol table implementation for my programming language is going smoothly.
Sometimes though, when I look at how other compilers approach certain features, I get the urge to do things differently.
I know it will bite me back eventually, but it's just that tempting.
Did you know `zig cc` might be a better C #compiler than #GCC / #Clang? And that you can use it to compile your #CGO-dependent #golang projects as well?
I just needed to cross-compile something for x86_64-linux-musl on aarch64-macos-none. Everything else kept giving me headaches (#docker, #qemu)… but using #zig just worked.
https://andrewkelley.me/post/zig-cc-powerful-drop-in-replacement-gcc-clang.html
If you're a prof who teaches multi/nanopass #compiler s, how do you manage the different versions of the files? Suppose you want to add a construct; now you have to propagate the change through every subsequent file, say. Just in general, how do you manage the different versions?
Das Ganze wird auch leicht philosophisch: Wir stellen uns die Frage was eigentlich ein Compiler ist und betrachten Compiler als Paradigma zur Problemlösung.
Diesen Samstag um 20:00 halte ich im Entropia einen Talk "Exotische Compiler von Hardware Synthese bis Genetik" in dem wir über ungewöhnliche Dinge die man mit Compilern machen kann reden. Wenn ihr Lust habt etwas über Compilerbau zu erfahren seid ihr herzlich eingeladen!
🎉 Welcome to "Unikernels #for Dummies" - because who doesn't want to spend their #weekend #learning about the world's most exciting #tech buzzwords? 🤖 Dive into this community-reviewed, best-effort opus on how to build a kernel, because *everyone* needs more #compiler #errors in their life! 🛠️
https://labs.iximiuz.com/tutorials/unikernels-intro-93976514 #Unikernels #Dummies #Buzzwords #HackerNews #ngated
The WebRacket language is a subset of Racket that compiles to WebAssembly
https://github.com/soegaard/webracket
#HackerNews #WebRacket #Racket #WebAssembly #Programming #Language #Compiler
Benchmarking a Baseline Fully-in-Place Functional Language Compiler [pdf]
https://trendsfp.github.io/papers/tfp26-paper-12.pdf
#HackerNews #Benchmarking #Functional #Language #Compiler #Compiler #Performance #Programming #Research #Tech #Trends
Benchmarking a Baseline Fully-in-Place Functional Language Compiler [pdf]
Want to contribute to Swift but don't know where to start? Discover an unexpected journey into compiler contributions and a clever workaround for fixing compiler bugs without changing the code.
🔗: https://massicotte.org/blog/compiler-changes-the-easy-way/ by Matt Massicotte (@mattiem)
I'm now to a point where the bootstrap transpiler (1700 lines of C) can compile the stage1 compiler (1700 lines of SPL) into a C program which can "compile" itself (in the sense that the frontend works, but the output is currently a textual representation of the AST).
Next step is to write a simple backend so I can get to a fully self-hosted state. Then I can iterate on stage1 and start building the full stage2 compiler, sharing the frontend with stage1 for bootstrapping.