the use of int for sys_exec was only needed for some intermediate

half-broken implementation of syscall/sysret; exec seems to work fine with syscall/sysret now.

the use of int for sys_exec was only needed for some intermediate
2992d6fe · Nickolai Zeldovich · cef3edd9 · 2992d6fe · 2992d6fe
--- a/kernel/sysfile.cc
+++ b/kernel/sysfile.cc
@@ -431,7 +431,7 @@ sys_chdir(const char *path)
  return 0;
 }
-//SYSCALL INT
+//SYSCALL
 int
 sys_exec(const char *upath, userptr<userptr<const char> > uargv)
 {

--- a/tools/syscalls.py
+++ b/tools/syscalls.py
@@ -55,13 +55,11 @@ SYS_%(uname)s = %(num)d
 .globl %(uname)s
 %(uname)s:
-  movq $%(num)d, %%rax""" % syscall.__dict__
+  movq $%(num)d, %%rax
-            if "INT" in syscall.flags:
+  movq %%rcx, %%r10
-                print "  int $T_SYSCALL"
+  syscall
-            else:
+  ret
-                print "  movq %rcx, %r10\n  syscall"
+""" % syscall.__dict__
-            print "  ret"
-            print
    if options.udecls:
        for syscall in syscalls: