From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10306142134.AA13400@clio.rice.edu>
Subject: Re: Integer Overflow
To: djgpp-workers AT delorie DOT com
Date: Sat, 14 Jun 2003 16:34:42 -0500 (CDT)
In-Reply-To: <7048-Sat14Jun2003152720+0300-eliz@elta.co.il> from "Eli Zaretskii" at Jun 14, 2003 03:27:21 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> I think there's no easy way of supporting INTO in the DPMI
> environment, but Charles should have the definitive answer to this.
> Currently, the Overflow exception is converted to SIGFPE.

As far as I know there should be no problem supporting INTO - it 
should just raise an exception.  You could probably just capture
SIGFPE and test for the appropriate things to jump out of the hander
if desired.  I'm away from home and don't have the resources to look
at it for the next several months, however.  Best thing to do is
create an experiment (probably hand added INTO assembler directive).