Solo5 status update, June 2017

gistfile1.txt

# Solo5 status update, June 2017

## Work in progress

1. ARM64 support (Solo5/solo5#193). This is waiting on further work by
Wei Chen after the latest round of reviews. I have also published WIP
branches of the MirageOS mid-layers (ocaml-freestanding,
mirage-solo5), see
https://github.com/solo5/solo5/issues/151#issuecomment-308451602.
Notably, it's unclear if the openlibm aarch64 support is of production
quality, and someone will need to implement an aarch64 `frexpl()` for
openlibm.

2. Cleanup/rewrite of the GDB server code by Ricardo
(Solo5/solo5#198). This is close to being ready for merging, but needs
a bit more work after the latest round of reviews.

3. Minimal refresh of Solo5 public APIs (Solo5/solo5#200, PR and most
discussion in Solo5/solo5#201). Looks like we have consensus here but
merging is a breaking API change so requires the OPAM upper bound
dance and new releases of the corresponding MirageOS mid-layers
(ocaml-freestanding, mirage-solo5, mirage-\*-solo5). As part of this
I'm also doing some long-needed cleanup of the Mirage/Solo5 bindings
which will need review. Work in progress branches of these changes are
in the tracking issue.

4. Muen Separation Kernel port (Solo5/solo5#194). The Solo5 code has
been merged, but this also requires new releases for the MirageOS
support, so I've deferred those until after/concurrently with (3).

In summary, lots of progress, breaking API changes coming up. I'll hop
on the release train for those after I get back from holiday.