There are entire [dissertations](http://www.kroening.com/diss/diss-kroe.pdf) dedicated to the subject matter of merely functionally verifying a pipeline (this doesn’t even consider out of order execution).
-Given the fact that performant bug-free processors no longer exist, how can you trust your processor? The next best thing is to have access to a processor’s design files. Not only have access to them, you must have the freedom to study, improve them, run the test suites and be able to improve those too. Not only that, you and everyone who has a stake in the success needs to be entirely free from NDAs and other restrictions which prevent and prohibit communication.
+Given the fact that performant bug-free processors no longer exist [1][2], how can you trust your processor? The next best thing is to have access to a processor’s design files. Not only have access to them, you must have the freedom to study, improve them, run the test suites and be able to improve those too. Not only that, you and everyone who has a stake in the success needs to be entirely free from NDAs and other restrictions which prevent and prohibit communication.
*Collaboration, not competition*.
Such a processor is referred to as a Libre processor. However, processors themselves are only a part of the picture. Nowadays, most contemporary computing tasks involve artificial intelligence, media consumption, wireless connectivity, etc... Thus, we must deliver an entire Libre-SOC.
-* <https://it.slashdot.org/story/20/03/09/2347202/amd-processors-from-2011-to-2019-vulnerable-to-two-new-attacks>
-* <https://it.slashdot.org/story/20/03/10/176200/intel-cpus-vulnerable-to-new-lvi-attacks#comments>
+* [1]: <https://it.slashdot.org/story/20/03/09/2347202/amd-processors-from-2011-to-2019-vulnerable-to-two-new-attacks>
+* [2]: <https://it.slashdot.org/story/20/03/10/176200/intel-cpus-vulnerable-to-new-lvi-attacks#comments>
# Benefits: Privacy, Safety-Critical, Peace of Mind...
projects / libreriscv.git / commitdiff