mirror of
git://sourceware.org/git/glibc.git
synced 2025-01-24 12:25:35 +08:00
b82ba2f011
That convention requires the instruction immediately preceding SYSCALL to initialize $v0 with the syscall number. Then if a restart triggers, $v0 will have been clobbered by the syscall interrupted, and needs to be reinititalized. The kernel will decrement the PC by 4 before switching back to the user mode so that $v0 has been reloaded before SYSCALL is executed again. This implies the place $v0 is loaded from must be preserved across a syscall, e.g. an immediate, static register, stack slot, etc. The restriction was lifted with Linux 2.6.36 kernel release and no special requirements are placed around the SYSCALL instruction anymore, however we still support older kernel binaries. |
||
|---|---|---|
| .. | ||
| aarch64 | ||
| alpha | ||
| am33 | ||
| arm | ||
| hppa | ||
| ia64 | ||
| m68k | ||
| mips | ||
| powerpc | ||
| tile | ||
| unix | ||