Viewing profile — gadmm
gadmm
HN member- Joined
- Wed, Feb 27, 2019, 11:35 PM UTC
- HN karma
- 42
- Public activity
- 17 items
- HN profile
- View on Hacker News ↗
About gadmm
Recent public activity
- story
-
comment
Comment #38526436
#9 (downgrading mut refs to shared refs) is a big one. It makes things quite a bit more complicated in the context of our work on the OCaml-Rust interface (more precisely the safe …
-
comment
Comment #35861540
The question is whether the user replacing `f(value)` with `if value == expected then f(expected) else f(value)` preserves program semantics. Look for Address dependency in Arm: se…
-
comment
Comment #35856659
This is about the classic trick of speculating on values using branch prediction (if value == expected then f(expected) else f(value)), which is always fun to see. But be careful i…
-
comment
Comment #34014220
To clear up any misconception, out of the box OCaml will behave like OCaml 4 with a single domain and a "domain lock". Programs currently using multiple threads for concurrency wil…
-
comment
Comment #31752598
The development of the OCaml-Rust interface is a bit organic. `ocaml-interop` aims to be a low-level but safe interface. At Inria we worked with the author to integrate ideas about…
-
comment
Comment #30057878
Baker's paper is visionary in that it announces a link between linear logic and move semantics for resources more than a decade in advance. As we know this was put into practice by…
-
comment
Comment #29881931
According to the paper “any compiler optimisation that breaks the load-to-store ordering is disallowed.”
-
comment
Comment #29877639
The "huge performance gains" refers to the prefetching optimisation, which is already in OCaml (the old OCaml 4 branch, not in multicore yet).
-
comment
Comment #29877545
As the paper clarifies, this is for the performance of non-atomic read/writes in sequential setting. The paper left the performance evaluation for atomic read/writes to future work…
- story
- story
- story
-
comment
Comment #27867551
We taught Rust at Masters-level as part of a course meant to show engineering students a variety of concepts from innovative programming language (there was also Haskell and Scala)…
-
comment
Comment #23766402
Indeed, OCaml multicore preserves the sequential low-latency setting, and this is important. Generalising this style is indeed a challenge, and I believe that there is something to…
-
comment
Comment #23750123
Regarding latency, beyond the kind of benchmarks proposed in the paper (from which this performance claim comes), keep in mind that the behaviour is qualitatively different between…
- story