So how was this breaking Go? Well, OR with 0

Question

So how was this breaking Go? Well, OR with 0

isn’t really a no-op. Since orq is not an atomic instruction, what really happens is the CPU reads the memory address and then writes it back. This creates a race condition. If other threads are running in parallel on other CPUs, orq might effectively wind up undoing a memory write that occurs simultaneously. Since the write was out of the stack bounds, it was likely intruding on other threads’ stacks or random data, and, when the stars line up, undoing a memory write. This is also why GOMAXPROCS=1 works around the issue, since that prevents two threads from effectively running Go code at the same time.

#backend #go #programming #russian

0

05.12.2017

1 ответов

12 просмотров

Пользователь 61a73 · Accepted Answer

Пользователь 61a73

Спасибо.

0

05.12.2017

170 похожих чатов

So how was this breaking Go? Well, OR with 0

1 ответов

Похожие вопросы