Date:	Tue, 18 Jan 2000 10:01:46 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	GAMMELJL AT SLU DOT EDU
cc:	djgpp AT delorie DOT com
Subject:	Re: AMD assembly language
In-Reply-To:	<01JKT1KTY2XE8WY342@SLU.EDU>
Message-ID:	<Pine.SUN.3.91.1000118095804.3041H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 17 Jan 2000 GAMMELJL AT SLU DOT EDU wrote:

>      The source codes were copied to a machine with an AMD K6 333
> mhz processor.  That machine has 92 mb of RAM.  The djgpp on that
> machine was downloaded in December 19,1999 (unzipped from
> djdev202.zip).  Presumably, this is the latest version of djgpp.

DJGPP version 2.03 was released about a week ago.

> Exiting due to signal SIGFPE 
> Division by Zero at eip=000040ef, x87 status=0120
> eax=00000000 ebx=00000000 ecx=00000036
>                     edx=00000005 esi=00000000 edi=00000038

This could be due to overflow in the mull or divl instructions.  It might 
be that AMD reacts to these problems differently than a genuine Intel 
chip.  I suggest to examine the code at the EIP=0x40ef in conjunction 
with the registers printed when the program crashes, and see if your 
inline assembly is safe enough for the kind of arguments you pass to it.

- Raw text -