From 69168c5934cd3f57bd93902c8ced6a01a3b0aebd Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Sun, 9 Feb 2020 17:07:07 +0100 Subject: microblaze: vfork syscall number is always available Due to the built-in tables, __NR_vfork is always defined, so the fork-based fallback code is never used. (It appears that the vfork system call was wired up when the port was contributed to the kernel.) --- sysdeps/unix/sysv/linux/microblaze/vfork.S | 4 ---- 1 file changed, 4 deletions(-) diff --git a/sysdeps/unix/sysv/linux/microblaze/vfork.S b/sysdeps/unix/sysv/linux/microblaze/vfork.S index 7bff659ff3..913aa06e2e 100644 --- a/sysdeps/unix/sysv/linux/microblaze/vfork.S +++ b/sysdeps/unix/sysv/linux/microblaze/vfork.S @@ -28,11 +28,7 @@ ENTRY (__vfork) -#ifdef __NR_vfork DO_CALL (vfork, 0) -#else - DO_CALL (fork, 0) -#endif addik r12,r0,-4095 cmpu r12,r12,r3 bgei r12,SYSCALL_ERROR_LABEL -- cgit 1.4.1