Calascibetta Romain

Just to clear the status of this PR: - In my mind, it's not really possible to deal with `sed` and `dune` at the same time. A use of `sed`...

Ok, the error is, indeed, not reproducible with the snippet of @hannesm but it is reproducible when we use: ```` (executable (name colink) (libraries hacl-star hacl_x25519))) ```` Into details, the...

> What's confusing me is why the symbols are appearing at link time at all, since hacl-star-raw appears to use ctypes-foreign to dynamically load them. I don't really understand underlayer...

The issue is more difficult than I imagined. Currently. the type `Name.t` has more an equivalence with a `string` than _a string which refer to a module name_. It seems...

Just to follow up a discussion with @Octachron, `Modname` was a nice idea but, due to the namespace integration, we have different view about a module: as a _filepath_ and...

As I said, even if the project compile with #37, it seems clear that we can not assert expected behaviors on OCaml 5.00.0 - and it becomes unsafe to use...

The CI works but it does not compile `gilbraltar` (only `gilbraltar-toolchain`). The main problem is: we need the OPAM layout to, finally, build our test and OCaml-CI does not provide...

As @avsm said, we currently need a cross compilation of C files provided by hacl to be able to compile tls (1.3 supports) in any targets (eg. Solo5 and Xen)....

> Mirage uses a dune-workspace file to cross compile all C bindings using special kernel CFLAGS, and that will just happen automatically if hacl is bundled with a dune file....

The current layout (see the `boot.S`) tries to use CPU0 and execute the main program on it with a specific stack position. Others cores are not used - but they...