Finding bugs in LLVM IR optimisers: programmatically generate small (loop free, no control flow) functions, run your favourite middle end passes, and verify the output is equivalent!
https://blog.regehr.org/archives/1510
(Uses Alive to verify and 4000 CPUs of compute.)
miniblog.
Related Posts
I've been using "Expected Int, but got String" for my type error messages, but I've been wondering if I could do better.
"Expected Int here, but this value has type String" or "This expression requires Int, but the value is String".
Do you have a favourite?
I've started keeping a list of particularly interesting bugs and patches that I've worked on: https://github.com/Wilfred/interesting-code
The time that I once removed *a single closing paren* in Emacs is still my favourite.
Do you have a favourite way of highlighting text in a CLI error message? Currently I'm using backticks, but I'm wondering what's the most readable.

