On Fri, Nov 29, 2019 at 10:12:10AM +0100, Thomas de Grivel wrote: > Maybe Go is not the only problem, I see SBCL compiling syscalls too. > > Truth is libc is for C and not all programs are written in C nowadays.
Where are you seeing SBCL compiling direct syscalls? In my testing, SBCL self-hosts just fine under a kernel modified to disallow syscalls from the text segment, whereas go is killed under such a kernel. Are you sure you're not seeing SBCL compile calls to the libc syscall wrappers?
