Re:Faster interpreters in Go: Catching up with C++
by uds5501 on Thursday March 20, 2025 @02:33PM
(#43427134)
I noticed the de-optimization bits when the compiler handles corner cases. How often did Vitess notice that the VM had to switch back to the old AST implementation?
[ Parent
| on HN ]
Re:Faster interpreters in Go: Catching up with C++
by tanoku on Thursday March 20, 2025 @03:16PM
(#43427675)
Very very seldomly! Obviously we need to be correct in 100% of the cases, which is why the de-optimizer is there, but in practice it just never triggers. Right now the things that trigger a deopt are very limited — malformed time literals, oferflowing integer negations and very little else. The performance impact is essentially zero.