Re: [golang-dev] Re: Moving Go to a newer NetBSD ABI in the 1.13 dev cycle

[Ian Lance Taylor <iant%golang.org@localhost>]

On Thu, Mar 7, 2019 at 7:32 AM Kamil Rytarowski <n54%gmx.com@localhost> wrote:
>
> On 07.03.2019 10:48, Benny Siegert wrote:
>
> > Any comments, objections, etc. from Go or NetBSD folks?
> >
>
> We should switch to libc calls and reduce users of syscall(2)/__syscall(2).

Go does work that way on Darwin, Solaris, AIX, and Windows.  It has an
efficiency cost--Go programs run somewhat slower--and it means that
someone has to write a bunch of near-boilerplate code (see, e.g.,
runtime/sys_darwin.go).  Is there a reason to go this route for
NetBSD?  Is NetBSD trying to avoid statically linked executables?

Ian