On Tue, Aug 21, 2018 at 8:03 AM, Nathan Sidwell <nat...@acm.org> wrote: > > 1) If we know we're using vfork, we can tell the parent directly via the > current stack frame and suitable use of volatiles.
I'm pretty reluctant to rely on this special behavior of vfork. A system could plausibly #define vfork fork and almost all programs would continue to work, but not this one. I think we would need a really compelling advantage to start doing handling vfork specially. But, since errors in this code are essentially non-existent, I don't see a compelling advantage here. Is there some larger scheme this is in aid of? Ian
