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
Date: Sat, 26 Jun 2004 20:23:08 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: higher-level IO very slow with cygwin1.dll 5.10 (due to set_flags?)
Message-ID: <20040627002308.GB21664@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <opr96vbqwilh6y6a AT localhost> <20040626154504 DOT GA961349 AT hpn5170x> <20040626160554 DOT GA980221 AT hpn5170x> <20040626170940 DOT GD20063 AT trixie DOT casa DOT cgf DOT cx> <20040626174145 DOT GA1032441 AT hpn5170x> <40DDEE8F DOT 7090707 AT ntlworld DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40DDEE8F.7090707@ntlworld.com>
User-Agent: Mutt/1.4.1i

On Sat, Jun 26, 2004 at 10:45:51PM +0100, Mark Thornton wrote:
>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  <dj AT cygnus DOT com>
>>>>	* 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?
>>I also assume that single threaded programs don't need the lock.
>> 
>Is the lock to ensure that normal POSIX append semantics are obtained
>when two processes are writing to the same file?  Normal win32
>behaviour would tend to overwrite whatever had been written by the
>other process

No.  newlib is supposed to be OS agnostic.  The locks are certainly
for multi-threaded purposes.

Anyone who is interested could always ask in the newlib mailing list.
newlib sourceware org.

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/