Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<01f001c16c12$3615e420$98ed85ce@amr.corp.intel.com>
From:	"Tim Prince" <tprince AT computer DOT org>
To:	"Charles Wilson" <cwilson AT ece DOT gatech DOT edu>, <cygwin AT cygwin DOT com>
References:	<3BF018AD DOT 9000105 AT ece DOT gatech DOT edu>
Subject:	Re: cygwin vfork
Date:	Mon, 12 Nov 2001 17:46:19 -0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200

----- Original Message -----
From: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
To: <cygwin AT cygwin DOT com>
Sent: Monday, November 12, 2001 10:45 AM
Subject: cygwin vfork


> Seen on the XEmacs list:
>
>  > In general the cygwin build is slower, I think this is for 3 main
>  > reasons:
>  >
>  > 1) gcc optimization is not as good as MSVC
>  > 2) The cygwin portability layer adds a lot of overhead especially
>  > wrt file handling.
>  > 3) The cygwin implementation of fork-and-exec doesn't jive well with
>  > the VM size of xemacs. Supposedly a real vfork is in the works for
>  > cygwin but I can't attest to its functionality.
>
> Does #3 make any sense?  I thought we *had* a real vfork...perhaps it
> doesn't work well with large apps?  Or is the author just blowing smoke?
>
> --Chuck
>
#1 doesn't make a great deal of sense either.  I suppose it's possible to
set up ground rules under which MSVC would optimize better than gcc, but
it's not my experience.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -