Thread

Platform-independent SIMD in Go

414 points · 152 comments · yurivish

fatty_patty89 · 1790342829 · focus · HN ↗
The problem with Go isn't performance but with the C/C++ interop overhead, even with the "30% less overhead" from a few updates ago which isnt true for 99% of cases, it isnt enough
1. victorbjorklund · 1790346359 · focus · HN ↗
  Why is that the case? I don’t know low level programming so why is Go limited in interop with C?
  1. fatty_patty89 · 1790350585 · focus · HN ↗
    its not limited but it has overhead because of the memory model of go doesnt match the C one so there has to be some sort of rerodering being done, that's what i understood atleast, and theres also the go concurrency
    assbuttbuttass · 1790429750 · focus · HN ↗
    The main problem is that Goroutine stacks are small, starting at 2KiB. When you're calling a C function, the Go runtime can't know how much stack space the C function will use, so it has to defensively expand the stack in a lot of cases
2. pjmlp · 1790351142 · focus · HN ↗
  Use Assembly instead of CGO, isn't that scary, back in the 8 bit days we were coding Assembly aged 10, on our Spectrum, C64, Atari, Apple, Acorn, MSX,....

Unofficial Hacker News client; not affiliated with Y Combinator.