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: <033d01c199de$4578ab10$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> Subject: Re: ksh on cygwin Date: Fri, 11 Jan 2002 00:54:06 +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: 10 Jan 2002 13:54:05.0927 (UTC) FILETIME=[44CEAF70:01C199DE] ----- Original Message ----- From: "Corinna Vinschen" > > - getpagesize() should return a value compatible with mmap(), that is dwAllocGranularity (65536) instead of dwPageSize (1024). > > We discussed that months ago. I think we're not going to change that > (it's 4096, not 1024, btw.). It will result in dubious problems > when a process mmaps a file. For instance, the latest gcc expects to > be able to read over the end of an mmaped file if the size is not a > multiple of getpagesize(). Now think of a file which is coincidentally > exactly 1 page long... I'm not sure what you are implying. unless getpagesize returns 1, the behaviour for gcc will be consistent for all larger sizes. If it's 4k, then a file that is 4k will behave the same way as a 64K file if the pagesize returned is 64k. You seem to be implying that something bad happens when the file size == the returned page size. What is that bad thing? 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/