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
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 21 Dec 2001 18:48:12 +0000
From:	Neil Booth <neil AT daikokuya DOT demon DOT co DOT uk>
To:	Werner Tuchan <tuwn AT gmx DOT net>, neil AT gcc DOT gnu DOT org, gcc-bugs AT gcc DOT gnu DOT org,
	gcc-gnats AT gcc DOT gnu DOT org, cygwin AT cygwin DOT com
Subject:	Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
Message-ID:	<20011221184812.A13959@daikokuya.demon.co.uk>
References:	<20011220002004 DOT 23509 DOT qmail AT sources DOT redhat DOT com> <000701c18964$fad2d2e0$fb4d0ed4 AT softron DOT de> <20011220183323 DOT B3065 AT daikokuya DOT demon DOT co DOT uk> <002b01c18a2d$aeb7d850$fb4d0ed4 AT softron DOT de> <20011221172007 DOT GA14954 AT redhat DOT com>
Mime-Version:	1.0
In-Reply-To:	<20011221172007.GA14954@redhat.com>
User-Agent:	Mutt/1.3.23i

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.

--
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 -