From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19112 invoked by alias); 21 Dec 2001 18:56:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 19087 invoked by uid 71); 21 Dec 2001 18:56:01 -0000 Date: Fri, 21 Dec 2001 10:56:00 -0000 Message-ID: <20011221185601.19083.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Neil Booth Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin Reply-To: Neil Booth X-SW-Source: 2001-12/txt/msg01046.txt.bz2 List-Id: The following reply was made to PR bootstrap/5149; it has been noted by GNATS. From: Neil Booth To: Werner Tuchan , neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, cygwin@cygwin.com Cc: Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin Date: Fri, 21 Dec 2001 18:48:12 +0000 Christopher Faylor wrote:- > Can I ask why we'd be reading beyond EOF? Is it guaranteed that bytes beyond > EOF will be zero on UNIX? This was discussed in September (see thread in gcc@ entitled "Bumming cycles out of parse_identifier"). It was decided that all known current Unix implementations have zeros until the next page boundary. Assuming EOF is indicated by a NUL is used as a lexer optimization. Neil.