Windows X86-64 System Call Table
How do they deal with the syscall numbers being different from release to release, while still maintaining binary compatibility?  From what I can tell, (in Linux at least) the syscall numbers are <i>the</i> thing that needs to stay constant for the kernel to not break user space.