Subject: Re: higher-level IO very slow with cygwin1.dll 5.10 (due to set_flags?)
From: Christopher Faylor <[email-masked]>
To: [email-masked]
Cc: "Pierre A. Humblet" <[email-masked]>
Date: Sat, 26 Jun 2004 15:37:10 -0400

On Sat, Jun 26, 2004 at 01:41:45PM -0400, Pierre A. Humblet wrote:
>On Sat, Jun 26, 2004 at 01:09:40PM -0400, Christopher Faylor wrote:
>> On Sat, Jun 26, 2004 at 12:05:54PM -0400, Pierre A. Humblet wrote:
>> >Beware, I found this:
>> >2000-05-19  DJ Delorie  <[email-masked]>
>> >	* libc/include/stdio.h: no getc/putc macros for cygwin; causes
>> >	compatibility issues with different dll versions
>> >so you may need to recompile when updating cygwin.
>> 
>> Also wouldn't that work around the file locks that were ostensibly put
>> there for a reason?
>
>That crossed my mind. But there is no file lock in the macro, which is
>used by systems other than cygwin. How do they manage it?

They may not care of about this.

>That issue may be a factor in the legendary slowness of Cygwin.

AFAICT, this lock was introduced in April so if it is part of the legend
it has grown to prominence very quickly.

cgf

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