3 ms·
Isn't this the route Golang famously went, with poor results? https://news.ycombinator.com/item?id=25997506 https://news.ycombinator.com/item?id=25997506 Appa
by remram 5y ago
Isn't this the route Golang famously went, with poor results?
https://news.ycombinator.com/item?id=25997506 https://news.ycombinator.com/item?id=25997506
Apparently for BSD, the ABI is not that stable, glibc works around bugs on some platforms (adding memory barriers etc), and there are security features that check the origin of syscalls. I wonder whether this is truly acceptable on Linux...
- matheusmoreira 5y agoIt is my understanding that Go attempted to perform direct system calls on systems where it was never supported. As a result, Go programs stopped working when the binary interface changed. This is not a problem on Linux. > glibc works around bugs on some platforms (adding memory barriers etc) That's really interesting. Do you have examples of such fixes? I'm more familiar with musl sources, glibc proved to be somewhat difficult to navigate.