Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3FF3F058.4A9AF6A7@dessent.net> Date: Thu, 01 Jan 2004 02:03:04 -0800 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Question about ash and getopts References: <200401010419.i014Jbqd016872@guild.plethora.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.linuxsv3.net X-AntiAbuse: Original Domain - cygwin.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - dessent.net X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Peter Seebach wrote: > Note also that, on the gcc configure script, the difference between /bin/sh > and bash is maybe 5 seconds on a script that takes nearly 3 minutes. It's > hard for me to imagine this being the source of the word "abysmal"; I'm > assuming something else was changed. Maybe different optimizer flags were > used on /bin/bash back then, which produced worse results? Or perhaps at the time the change was made fork/vfork was not nearly as optimized as it is now. FWIW I was reading the archives about when /bin/sh became ash, and it was sometime between B18 and B19, so late 1997/early 1998. That's going on six years ago, and I'm sure there have been plenty of core optimizations since. Brian (oh, and happy new year and thanks for everyone's work on Cygwin) -- 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/