News for hackers. Stuff that matters.
Re:Problems with the Golang runtime and toolchain by ori_b on Tuesday January 06, 2015 @05:22PM (#8847499)
> The Solaris port was definitely slowed down by the fact that on other Unix systems, Go encodes the system call table.

Is there any reason that you can't just encode the system call table on Solaris too?

Re:Problems with the Golang runtime and toolchain by 4ad on Thursday January 08, 2015 @07:30AM (#8856089)
Yes, unlike Linux, the system call table is not guaranteed to be stable. Also, libc does a lot of things, like set up TLS. It's also critical in the signalling path.
Re:Problems with the Golang runtime and toolchain by ori_b on Thursday January 08, 2015 @12:40PM (#8857594)
If the system call table isn't stable, how can you ship statically linked binaries?
Re:Problems with the Golang runtime and toolchain by 4ad on Thursday January 08, 2015 @12:53PM (#8857694)
On Solaris you don't ship statically linked binaries. All Go binaries are linked with libc.so. In fact, amd64 Solaris doesn't even support statically linked binaries at all. It won't exec them.

The situation is exactly the same as on Windows. Windows Go binaries are dynamically linked agains Windows standard libraries, and Go binaries use the shared libraries instead of doing system calls themselves.