Date: Mon, 8 May 2000 14:35:55 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Perfomance of gc-simple
In-Reply-To: <200005080919.LAA04200@lws256.lu.erisoft.se>
Message-ID: <Pine.SUN.3.91.1000508143216.3080C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 8 May 2000, Martin Stromberg wrote:

> Eli said:
> > As for mmap, it should be trivial to throw together a KISS[1] 
> > implementation that simply reads the entire file into memory, and see 
> > how well (or how badly ;-) does that work, especially with very large 
> > sources.
> 
> Hey, this means we can support mmap( ..., PROT_READ, ... ),
> i. e. read-only mmap()!

In principle, yes.  However, before we put mmap into the library, I think 
Someone (tm) should look at several GNU packages which use mmap and 
verify that our minimal implementation will do what those packages 
expect.  Since the availability of mmap is checked by the configure 
script by linking a program, and since GNU packages I've seen always 
prefer to use mmap if it is found, if we put mmap into the library for 
GCC, we had better made sure it doesn't bite us elsewhere.