Message-ID: <5003D86E.3060905@users.sourceforge.net>
Date: Mon, 16 Jul 2012 04:01:34 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: compiling coreutils with cygport
References: <CAMkU=1yRPm7vu30taP6Y0xNy3BRZxVOYUAL_aMCo794SSbGb6Q@mail.gmail.com> <50009B44.4060504@redhat.com>
In-Reply-To: <50009B44.4060504@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 2012-07-13 17:03, Eric Blake wrote:
> Actually, coreutils tries to use all the *_unlocked variants of stdio,
> since those have better speed in single-threaded programs (all but sort
> are single-threaded, and sort skips stdio).  I do know that cygwin has
> putchar_unlocked, but does not have quite as many *_unlocked variants as
> Linux, so it may be a case where the configure logic to detect _unlocked
> functions went wrong and cygwin ends up using putchar instead of
> putchar_unlocked as a result.  I'll have to look into it more.

Currently we have the four required by POSIX: getc_unlocked, 
getchar_unlocked, putc_unlocked, and putchar_unlocked.  A little while 
ago I was working on the others which are available in Linux, as gcc 
will use them if available, but they didn't seem to make much difference 
to gcc's performance.  I still have that work locally, so if these would 
be useful, I could try to finish them up.


Yaakov

--
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