> > I looked at the hpux implementation and it doesn't create a frame. > > Of course, the vfork syscall then must not clobber the return address, > > etc. > > Yes, the vfork syscall *must not* clobber r2, without a stack we have > nowhere to save it. I'm pretty sure the kernel preserves r2 across a > vfork. The next step is to verify that :-) Actually, it's ok to save it in the __fork caller's frame at the standard location. r2 is always saved there by the callee. The argument slots for r26 thru r23 and the PIC register slot also can be used. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
