This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: use posix_spawn in pexecute


On Mar 12, 2002, Zack Weinberg <zack@codesourcery.com> wrote:

> I wouldn't have a problem with a pexecute implementation marked #ifdef
> __hurd__ that used posix_spawn.  My objection is to penalizing systems
> with a fast fork primitive, that happen to have posix_spawn also.

Ha!  It sounds much more reasonable when put this way :-)

Still, I don't see how `posix_spawn' could not be as efficient as
the usual fork/exec pair, since implementing one in terms of another
would be the obvious choice if there's no more efficient way to do
it.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]