Skip to contentSkip to conversation

x86_64: remove dup syscall

PATCH In review [email protected] 2 participants 2 messages Mar 30, 2005

lore
Share & tools
lore
#0 lore raw

PATCH 3/3 x86_64: remove dup syscall

Remove duplicated syscall entry.

This likely affects compilation with older GCC's (2.95.x), since in arch/x86_64/kernel/syscall.c this will result in assigning twice the same array element.

By experience, this works with newer GCC's but not with 2.95.3/4.

---

 linux-2.6.11-paolo/include/asm-x86_64/unistd.h |    2 --
 1 files changed, 2 deletions(-)
include/asm-x86_64/unistd.h renamed from include/asm-x86_64/unistd.h~remove-dup-sc +0 -2
diff -puN include/asm-x86_64/unistd.h~remove-dup-sc include/asm-x86_64/unistd.h
@@ -533,8 +533,6 @@ __SYSCALL(__NR_tgkill, sys_tgkill)
 __SYSCALL(__NR_utimes, sys_utimes)
 #define __NR_vserver		236
 __SYSCALL(__NR_vserver, sys_ni_syscall)
-#define __NR_vserver		236
-__SYSCALL(__NR_vserver, sys_ni_syscall)
 #define __NR_mbind 		237
 __SYSCALL(__NR_mbind, sys_mbind)
 #define __NR_set_mempolicy 	238

_

#1 lore raw
Quoted 8 lines · On Wed, Mar 30, 2005 at 07:32:18PM +0200, [email protected] wrote:

Remove duplicated syscall entry.

This likely affects compilation with older GCC's (2.95.x), since in arch/x86_64/kernel/syscall.c this will result in assigning twice the same array element.

By experience, this works with newer GCC's but not with 2.95.3/4.

gcc 3.0 was the first release to support x86-64.

Dave