[This piece is co-authored with Vsevolod Livinskii.] Formal verification isn’t some sort of magic pixie dust that we sprinkle over a computer system to make it better. Real formal verification involves a lot of the same kind of difficult, nasty, grungy engineering work that any other systems-level job involves…
Visit blog.regehr.org → RSS feedOn Hacker News May 2010 – Aug 2023
Software Engineering 34Programming Languages 20Systems & Performance 8Life, Learning & Writing 6Security & Privacy 5Career & Management 3
My hope would be option 1 for application code (as opposed to the “systems code” that you have there): fewer and fewer people use these languages to write application code. Moreover, I think that’s probably happening to some extent.
An “optimizer” should really be called an “improver”, and a “superoptimizer” should be called an “optimizer” 🙂
Hello, My name is Nadav and I am a PhD candidate, researching compilers for embedded systems and high-level synthesis. This is an excellent post and I enjoyed reading it. I have a few comments. 1. I agree about verification and optimization joining forces. We already see it to some extent with compiler warnings. 2…