X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=ZmV/AxwR0/JlQB3NjHzRWFDBuyU9iowbtxac4PngfUVmJxpjqwzB+
	ed/nGZi2bSaLKU1hIWfubmLcajuap64XvsLaqU6sIuvuAYplWf3oxA3W9VnP3xeb
	zi2HioXh24eVURZtvQQcITq7SmUYOQ5dc6MIejaXiXx+9tUq4Y2Zjc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=573rjEmddSiZ0SlvLcAO4Arb+l8=; b=goLAFYYKH89POsHFevlSdoOH3zHV
	hpg2ACgQpOf8BUKOAwbh5MN7WT8ypQ/BRf4rdaU6FuDz1unnEPpTxCj4630zJDXu
	5GfbsJ/cUqP1j38ZlodjIVqUgFFeS903r0oRe8zFxMKQ2JJ9FU18ojLFgE/u98ZD
	NCurx9vfSAFGd8s=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SEMBACKSCATTER autolearn=no version=3.3.1
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19odG4B6W3hgRBPJ+APhxLc
Date: Tue, 21 May 2013 02:18:16 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: BUG: Ability to access nonexistent directories
Message-ID: <20130521061816.GC3786@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <000201ce52c4$891b04c0$9b510e40$%fedin AT samsung DOT com> <20130517083612 DOT GE21752 AT calimero DOT vinschen DOT de> <000d01ce52dc$74e54bb0$5eafe310$%fedin AT samsung DOT com> <20130517102655 DOT GG21752 AT calimero DOT vinschen DOT de> <20130517145612 DOT GC7087 AT ednor DOT casa DOT cgf DOT cx> <001a01ce5550$9e20afd0$da620f70$%fedin AT samsung DOT com> <519A3E58 DOT 4010609 AT cygwin DOT com> <000101ce55e9$6ab6f840$4024e8c0$%fedin AT samsung DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000101ce55e9$6ab6f840$4024e8c0$%fedin@samsung.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, May 21, 2013 at 10:07:03AM +0400, Fedin Pavel wrote:
>> Not to discourage you but there will be a fairly low tolerance for much
>> of a complexity change or almost any performance degradation.  Cygwin's
>> performance is a regular source of complaints on this list (and
>> elsewhere).
>
> By the way... Right now i'm testing 64-bit Cygwin, and it appears to be
>significantly faster. I wonder, did you do anything special to achieve this
>? Or does this mean just that 32-bit API on 64-bit Windows is slow ?

The 64-bit port employed fewer hippos.  As it turns out, they were terrible
coders.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple