=== ----- Original Message ----- From: "Corinna Vinschen" <[EMAIL PROTECTED]>
> 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/
