shym

I had no time to make any progress on that work. (I imagine the changes in that PR will be required anyway even if they are not enough.)

That would be great indeed! To make sure that I understand: would changing only the declaration to be strong already have an impact on the native ports? (Clearly changing the...

Thinking about it, maybe this issue should be reported against `lib-musl`, as I’ve run into it when the main thread of a program calls `pthread_exit`. I’m not sure which layer...

I would suggest to follow the same strategy than what was merged in the compiler in [ocaml/ocaml#13735], namely to do just as the C compiler does: the logic the C...

The issue is really in Solo5. The patches to OCaml fixed this issue in the code generated by the compiler. The fix in the compiler is doing something similar to...

> Any PR that fixes the warning would be great. #619 is what I had in mind.

I forced a retry on the CI failures: all the remaining CI errors are due to the incompatibility between dune 3.17.2 and OCaml 5.4.0~alpha1.

I’ve [added `solo5-virtio` to the network benchmarks](https://github.com/shym/mirage-skeleton/tree/virtio-bench) we had run and ran it both with the released Solo5 and this PR. I get the following results. @dinosaure: did you see...

> > * In [a0933f2](https://github.com/ocaml/ocaml/commit/a0933f257884569bcb6c36b207bed743fa405ef0), installation of native DLLs is removed: was that on purpose? > > Oo, it's intentional (they should never have been being installed in the first...

> This is excellent :pray: > Thinking a bit a head, one could imagine having a "pure-Cygwin" CI workflow too at some future point? 🤔 At that point, we might...