Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	Wed, 1 Jan 2003 18:56:23 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: read() syscall broken on faster cpu?
Message-ID:	<20030101235623.GA24893@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<011401c2b1e4$67153c60$e185fea9 AT oemcomputer>
Mime-Version:	1.0
In-Reply-To:	<011401c2b1e4$67153c60$e185fea9@oemcomputer>
User-Agent:	Mutt/1.5.1i

On Wed, Jan 01, 2003 at 11:23:24PM +0100, Sascha Sommer wrote:
>Is it possible, that the read() syscall sometimes doesn't work correctly on
>newer cpus?

No.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -