3 ms·
On FreeBSD, it's supported but kinda sucks. e.g., porting to a new CPU architecture is hell (I contributed to the FreeBSD/aarch64 go port, someone else picked i
by floatboth 8y ago
On FreeBSD, it's supported but kinda sucks. e.g., porting to a new CPU architecture is hell (I contributed to the FreeBSD/aarch64 go port, someone else picked it up now…)
The libc is the stable ABI on pretty much any OS that's not called Linux, just use it.
- yjftsjthsd-h 8y agoOkay, but now you're using a C library as the basis for your non-C programming language. I understand why it is that way, but that kind of sucks.
- floatboth 8y agoEhh… does it kind of suck? The ABI of libc's syscall wrappers is basically "here's some ELF symbols to call with some arguments using the operating system's preferred calling convention". The only really "C" thing about it, other than the name, is struct layouts of various arguments.