Which platform are you talking about? As far as I know on amd64 we always use the SYSCALL instruction.

386 (aka x86) https://github.com/golang/go/blob/master/src/syscall/asm_linux_386.s

Current Minimum Go CPU requirement for 386 is Pentium MMX which does not support sysenter.
Therefore changing this for all supported Go archs would need a test for the specific CPUID bit and a bump in minimum CPU requirements. https://golang.org/doc/install/source#environment

See

// Most linux systems use glibc's dynamic linker, which puts the
// __kernel_vsyscall vdso helper at 0x10(GS) for easy access from position
// independent code and setldt in runtime does the same in the statically
// linked case. However, systems that use alternative libc such as Android's
// bionic and musl, do not save the helper anywhere, and so the only way to
// invoke a syscall from position independent code is boring old int $0x80
// (which is also what syscall wrappers in bionic/musl use).
//
// The benchmarks also showed that using int $0x80 is as fast as calling
// *%gs:0x10 except on AMD Opteron. See https://golang.org/cl/19833
// for the benchmark program and raw data.

Are there new benchmarks showing Go to better off not using int 0x80 with an alternative supported with bionic, musl and position independent code? This would be interesting especially on CPUs that dont support amd64 as the newer ones are likely to be mostly used with the amd64 arch which supports sysenter.

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)