I think the only way to tackle this problem in a scalable manner is if programming language maintainers offer formal verification of their programs. I don't th

I think the only way to tackle this problem in a scalable manner is if programming language maintainers offer formal verification of their programs. I don't think this will work in LLVM based compilers (due to the nature of how a backend compiler is being implemented for each platform and architecture), but maybe we should take a closer look at ADA Spark, or maybe we should try to focus our efforts on satisfiability resolvers that can point out common mistakes? Golang kind of made the right first step with their vulnerability checker that is AST aware and can point out methods and signatures that are known to be affected. There's also a lot of complexities behind decompilation aspects so I don't think C ABIs will be enough in the future, and a more data type aware format is probably needed.