public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/5149: gcc-20011217 reads beyond EOF on cygwin
Date: Fri, 21 Dec 2001 10:56:00 -0000	[thread overview]
Message-ID: <20011221185601.19083.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/5149; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Werner Tuchan <tuwn@gmx.net>, 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.


             reply	other threads:[~2001-12-21 18:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21 10:56 Neil Booth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-19  4:26 neil
2001-12-21 23:36 Zack Weinberg
2001-12-21  9:26 Christopher Faylor
2001-12-21  6:46 Werner Tuchan
2001-12-20 11:16 Neil Booth
2001-12-20 11:06 Zack Weinberg
2001-12-20 10:36 Neil Booth
2001-12-20  6:46 Werner Tuchan
2001-12-19 16:20 neil
2001-12-18  3:56 tuwn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011221185601.19083.qmail@sources.redhat.com \
    --to=neil@daikokuya.demon.co.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).