Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <081501c19a8e$6c341270$0200a8c0@lifelesswks> From: "Robert Collins" To: "Corinna Vinschen" References: <200201101259 DOT g0ACxFN12728 AT dymwsm10 DOT mailwatch DOT com> <20020110144551 DOT J12057 AT cygbert DOT vinschen DOT de> <033d01c199de$4578ab10$0200a8c0 AT lifelesswks> <20020110150729 DOT L12057 AT cygbert DOT vinschen DOT de> <07f601c19a8b$56af1150$0200a8c0 AT lifelesswks> <20020111114926 DOT X12057 AT cygbert DOT vinschen DOT de> Subject: Re: ksh on cygwin Date: Fri, 11 Jan 2002 21:55:02 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 11 Jan 2002 10:55:00.0783 (UTC) FILETIME=[6A9D93F0:01C19A8E] === ----- Original Message ----- From: "Corinna Vinschen" > Now, the pagesize on Windows is 4K. If the file size is coincidentally > 4096 or 8192 or any other multiple of 4K, gcc knows that it has to > fallback to it's "slow" method since getpagesize() has returned the > correct value. If we change getpagesize() to return the granularity > (64K) instead of the pagesize, gcc would wrongly assume that the > file doesn't exactly match the pagesize so it would assume that > it can use the "fast" method and would expect a trailing 0 byte. Now I get it! Thanks. Rob -- 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/