X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Date: Mon, 13 Dec 2004 11:28:41 +0200 (EET)
From: Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
Sender: peuha AT sirppi DOT helsinki DOT fi
To: djgpp-workers AT delorie DOT com
Subject: Re: Bison 1.875 (release 2)
In-Reply-To: <01c4df08$Blat.v2.2.2$4ed91b00@zahav.net.il>
Message-ID: <Pine.OSF.4.58.0412131117330.26801@sirppi.helsinki.fi>
References: <5CDCE8E138ACB445B11E9F7B85FC782A1AAB8A AT radon DOT smr DOT intern>
 <01c4deae$Blat.v2.2.2$99d27980 AT zahav DOT net DOT il> <41B9977F DOT AE71420B AT yahoo DOT com>
 <01c4df08$Blat.v2.2.2$4ed91b00 AT zahav DOT net DOT il>
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 Sat, 11 Dec 2004, Eli Zaretskii wrote:

> The only limitation of this technique, IIRC, is that you can only
> unmap page-aligned regions of memory.  This leaves the portion of
> memory between the end of the allocated buffer and the next page
> unprotected on the hardware level.

YAMD can align either the beginning or the end of each allocated buffer
at page boundary, so this is no problem, although you have to run the
program twice to test it thoroughly.  The default is to align the end of
each buffer, because access after the end is more common than before the
beginning.  (If pointers could have individual selectors, it would be
possible to use the same technique under any DPMI host since even pure
DPMI 0.9 supports selector limits, but unfortunately GCC doesn't produce
such code.)

-- 
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/