KC Sivaramakrishnan

@fondation451 I've reorganized the library structure for jbuilder. Looks like this is conflicting with the PR. Could you look into this?

What @avsm says is correct except for a small clarfification: > malloc-allocated and not stuck in the minor heap Any object larger than [`Config.max_young_wosize`](https://ocaml.org/api/compilerlibref/Config.html#VALmax_young_wosize) gets allocated in the _major heap_,...

Makes sense. See #5.

Reopening this issue. Unsurprisingly, it turns out implementing lock-free k-CAS is tricky. Helpfully, there is a paper about this very issue: > http://www.cl.cam.ac.uk/research/srg/netos/papers/2002-casn.pdf > It takes 3n+1 CAS operations to...

Thanks for the bug report. `kcas` and `reagents` are not actively maintained now as the multicore team does not have the resources to do so. We will have to come...

> Symmetrically, I wonder whether we can break the GC invariants here. On the second initialization, we're overwriting values computed during the first initialization, but not going through caml_modify, so...

For someone new to the OCaml compiler who is building the compiler from sources, the path that they may take is `README.adoc -> INSTALL.adoc` to [this section](https://github.com/ocaml/ocaml/blob/trunk/INSTALL.adoc#building-the-compiler). Perhaps adding a...

Yes. I was looking at this a few weeks ago, and I am still interested in doing this. I did have a few questions regarding this: - How/when do objects...

> Is anyone planning to have a look? Not this week as I am busy with other things.

> what's the issue if the wrapper allocates? It is not about allocations, but from where the exception gets raised. The idea in https://github.com/ocaml-multicore/ocaml-multicore/pull/437 is to avoid the slower "possibly-allocates-or-raises"...