Date: Wed, 2 Jun 1999 09:45:28 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp-workers AT delorie DOT com
Subject: Re: __dpmi_simulate_real_mode_procedure_retf_stack
In-Reply-To: <9906011347.AA15174@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.990602094502.29915A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 1 Jun 1999, Charles Sandmann wrote:

> > The source code of __dpmi_simulate_real_mode_procedure_retf_stack is
> > attached below.  Unless I'm missing something, it passes the number of
> > *bytes* on the stack in ECX, whereas the DPMI Spec says we need to
> > pass the number of 16-bit *words* (see the excerpt below).
> 
> I suggest this should be documentation defect and the code stay the
> way it is, so working code does not get the stack size cut in half.

Won't that cause crashes and other trouble?  The DPMI host will see
the value of ECX and copy that many words onto the RM stack.  Are we
sure there will be enough stack space to push twice the amount of
data?  The DPMI spec seems to ensure only 30 words of stack provided
by the DPMI host, and recommends to put non-zero values into the RM
SS:SP beyond that.