Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Checked C. Parent comment
[1] https://staff.aist.go.jp/y.oiwa/FailSafeC/index-en.html
[2] https://people.cs.rutgers.edu/~sn349/softbound/
The former apparently implements full ANSI C, and the latter apparently has a memory safety proof in Coq.
The group that did [1] also did an ANSI C to Java compiler.
It seems to me that we could really use a safe ABI (x86_64_safe, etc.) for C/C++, and that it should be supported by clang and gcc.
Maybe CHERI will catch on someday...
There are no comments on this comment yet.
[1] https://staff.aist.go.jp/y.oiwa/FailSafeC/index-en.html
[2] https://people.cs.rutgers.edu/~sn349/softbound/
The former apparently implements full ANSI C, and the latter apparently has a memory safety proof in Coq.
The group that did [1] also did an ANSI C to Java compiler.
It seems to me that we could really use a safe ABI (x86_64_safe, etc.) for C/C++, and that it should be supported by clang and gcc.
Maybe CHERI will catch on someday...