3 ms·
I might. My idea is to use either it or more pure ML/Ocaml to code the prototype up then convert each function into imperative C, Rust, or Ada. I figure a subse
by nickpsecurity 11y ago
I might. My idea is to use either it or more pure ML/Ocaml to code the prototype up then convert each function into imperative C, Rust, or Ada. I figure a subset of Haskell should make that achievable. So, I can use all the tools like QuickCheck and QuickSpec for Haskell along with functional style to knock out many issues. Then, direct translation to imperative with no global issues, equivalence testing generated from Haskell tests, and static analysis to ensure local code is proper.
That seL4 matched Haskell and C... along with open-sourcing a key tool (AutoCorres)... makes me think this is achievable. My method isn't formal proof but would be more accessible. What do you think?
- pjmlp 11y agoYou can already generate C from Haskell using jhc compiler: http://repetae.net/computer/jhc/ http://repetae.net/computer/jhc/ It doesn't support all the language features, though. Besides their standard one, GHC also has an additional LLVM and an older, now deprecated, C backends: https://downloads.haskell.org/~ghc/7.6.3/docs/html/users_guide/code-generators.html https://downloads.haskell.org/~ghc/7.6.3/docs/html/users_gui... The UHC also has a C backend, but not fully implemented, http://foswiki.cs.uu.nl/foswiki/Ehc/UhcUserDocumentation#A_6.6.1_61C_61:_GRIN_based_C_44_with_whole_program_analysis http://foswiki.cs.uu.nl/foswiki/Ehc/UhcUserDocumentation#A_6... Sounds a good idea, on the other hand have you ever used Frama-C? Never used it, but it seems being used in this kind of scenarios.
- nickpsecurity 11y agoThanks for links. So, here we go. re generating C. The key thing is whether it generates human-readable and -editable C. Most of those tools are used to just feed and piggyback on a C compiler. In my scheme, the Haskell is like the high-level, executable spec with C being equivalent. Such tools might be a start on my goal. I like that JHC has no garbage collector. That's promising for same reason Rust having no GC is. :) re Frama-C. Oh, yeah, that's good thinking as it's already been used for plenty C verification, even standard library. I was thinking of encoding Haskell specs in Frama-C somehow but not sure as I'm not formal methods specialist. Anyway, you might like where such techniques got their start for mainstream languages: http://apotheca.hpl.hp.com/ftp/pub/dec/SRC/research-reports/SRC-159.pdf http://apotheca.hpl.hp.com/ftp/pub/dec/SRC/research-reports/...
- the_why_of_y 11y agoGHC's C backend did not by any means generate anything a human would enjoy reading. It ran fast, though, on several platforms, which was the point.
- nickpsecurity 11y agoAs I suspected. Thanks for the confirmation. I'm guessing human-readable output might have to be done at an earlier stage in the compiler to keep it close to original code. Or do it high-assurance style with each intermediate representation in C to let reader see what transformed code means.
- pjmlp 11y agoThanks for the link. I really appreciate HP has kept DEC papers alive, they are my main source into Modula-3 universe, but they are hard to search for. Another possibility using something like the "Tiger book" and write a ML -> C compiler for the C subset you care about, but by then maybe contributing to Ada (GNAT), Rust or Swift would be better use of time. I also forgot to mention on my previous comment that Idris and F* also have C backends, but they might suffer from the same problems.
- nickpsecurity 11y agoBtw, discovered something trying to update my research collection for memory safety and static analysis. Turns out, a prior technique for analyzing C that looked promising also has a Haskell project. That's Liquid Types. Links describing it & to various projects http://goto.ucsd.edu/~rjhala/liquid/haskell/blog/about/ http://goto.ucsd.edu/~rjhala/liquid/haskell/blog/about/ C verifier download http://goto.ucsd.edu/csolve/ http://goto.ucsd.edu/csolve/