Patchwork [26/26] microblaze: vfork is always available

login
register
mail settings
Submitter Florian Weimer
Date Feb. 9, 2020, 8:21 p.m.
Message ID <b59c4d3ad6448be3db09f92c36fbe29edb1f18b1.1581279333.git.fweimer@redhat.com>
Download mbox | patch
Permalink /patch/37830/
State New
Headers show

Comments

Florian Weimer - Feb. 9, 2020, 8:21 p.m.
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(-)

Patch

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