This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
- 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
- Date: Fri, 21 Dec 2001 18:48:12 +0000
- Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
- References: <20011220002004.23509.qmail@sources.redhat.com> <000701c18964$fad2d2e0$fb4d0ed4@softron.de> <20011220183323.B3065@daikokuya.demon.co.uk> <002b01c18a2d$aeb7d850$fb4d0ed4@softron.de> <20011221172007.GA14954@redhat.com>
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/