X-Spam-Check-By: sourceware.org
Message-ID: <4536FCC8.6000606@qualcomm.com>
Date: Wed, 18 Oct 2006 21:19:20 -0700
From: Rob Walker <rwalker AT qualcomm DOT com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: igncr vs text mode mounts, performance vs compatibility
References: <1160655422743 DOT antti DOT nospam DOT 1605718 DOT wGO_WJ9D1NlId3tB-z6Qig AT luukku DOT com> <20061012123406 DOT GA30908 AT trixie DOT casa DOT cgf DOT cx> <452EA386 DOT 9010201 AT qualcomm DOT com> <20061012212011 DOT GA8535 AT trixie DOT casa DOT cgf DOT cx> <452EFDDB DOT 1010301 AT qualcomm DOT com> <452F8719 DOT 9060300 AT cygwin DOT com> <4536BC88 DOT 3030003 AT qualcomm DOT com> <4536C922 DOT 4090807 AT qualcomm DOT com> <4536CECC DOT F126C397 AT dessent DOT net>
In-Reply-To: <4536CECC.F126C397@dessent.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Thanks for reading, Brian.  Apologies to all that my recent tend to bulk.

The point of my post was to advocate igncr as the default for bash 3.  I 
realize I'm not alone in this advocacy.  I'm truly happy that bash 3 is 
super fast compared to bash 2, but bash 3's "incompatibility" is 
currently a (possibly serious for me) stumbling block.

What motivated today's work was the bash 3.2 announcement, which 
(apparently) doesn't make igncr the default.  Eric, what's your current 
thinking on this topic?

-Rob

Brian Dessent wrote:
> Rob Walker wrote:
>
>   
>> I looked into my scripts a little harder, have better results, some new
>> conclusions:
>>     
>
> I think you are missing the point somewhat.  The thing you need to
> benchmark against is the older bash version before the 'igncr' option
> even existed, which read every script one byte at a time regardless of
> mount type or line endings.  With typical 'configure' scripts easily
> exceeding 200 kB (and some more than 2.5 MB!), this resulted in massive
> overhead.  *That* was the performance hit that motivated this whole
> ordeal in the first place.
>
> I understand you are advocating for igncr being set by default, but I
> got the impression that everyone agreed that this would probably be a
> good idea, and that Eric would probably make this the default
> eventually.
>
> Brian
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>   


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