microblaze: vfork 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.)

Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>

diff --git a/sysdeps/unix/sysv/linux/microblaze/vfork.S b/sysdeps/unix/sysv/linux/microblaze/vfork.S
index 7bff659ff359de6b30e81ef0a0dea0c6d57bb087..913aa06e2e2952c7ff3cdaf61f019667b312514a 100644 (file)
--- 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