From: "Benjamin Kalytta" <bkausbk AT web DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: extended assembler
Date: Sat, 13 Oct 2001 14:10:02 +0200
Organization: T-Online
Lines: 12
Message-ID: <9q9b3f$oj8$03$1@news.t-online.com>
References: <9q8418$23s$00$1 AT news DOT t-online DOT com> <200110130121 DOT f9D1LmY19834 AT envy DOT delorie DOT com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Trace: news.t-online.com 1002975151 03 25192 jBuWSoJGSOYbb- 011013 12:12:31
X-Complaints-To: abuse AT t-online DOT com
X-Sender: 520031135094-0001 AT t-dialin DOT net
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

: Pretty much *any* function is going to change the value of %edx, so
: gcc is warning you that explicitly using %edx is asking for trouble.
: Especially when you create a global %edx register variable, since
gcc
: can't guarantee that it has the right value at all times.

yes I know this problem, but edx only will be changed before return
call ... before function exit. And with extended assembly it is
possible to mark this register as "changed".

benjamin