https://www.sqlite.org/testing.html
The testing each release goes through is quite impressive. I bet more time is spent on testing (or writing tests) than actually developing the features.
The testing each release goes through is quite impressive. I bet more time is spent on testing (or writing tests) than actually developing the features.
Of course who knows what your CPU microcode is doing, but for the question at hand—ensuring a highly portable C library does what it claims to do more efficiently and accurately than exhaustive testing—formal verification is certainly a reasonable approach.
Additionally, the majority of that test code is closed source, so it isn't getting run on nearly all the platforms sel4 supports anyway.