From: Ben Peddell <killer DOT lightspeed AT bigpond DOT com>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: One final inline assembly constraint question.
References: <84e4e2a9 DOT 0307242201 DOT 4c8dbb84 AT posting DOT google DOT com> <2c7Ua.13946$OM3 DOT 3560 AT news-server DOT bigpond DOT net DOT au> <84e4e2a9 DOT 0307260928 DOT 217a9482 AT posting DOT google DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 31
Message-ID: <IbTUa.18616$OM3.11006@news-server.bigpond.net.au>
Date: Sun, 27 Jul 2003 16:35:52 GMT
NNTP-Posting-Host: 144.134.89.37
X-Complaints-To: abuse AT bigpond DOT net DOT au
X-Trace: news-server.bigpond.net.au 1059323752 144.134.89.37 (Mon, 28 Jul 2003 02:35:52 EST)
NNTP-Posting-Date: Mon, 28 Jul 2003 02:35:52 EST
Organization: BigPond Internet Services
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Joel wrote:
> Ben Peddell <killer DOT lightspeed AT bigpond DOT com> wrote in message news:<2c7Ua.13946$OM3 DOT 3560 AT news-server DOT bigpond DOT net DOT au>...
> 
>>Joel wrote:
>>
>>>I have read up on, and am now pretty familiar with the usual "a" =
>>>eax, "S" = esi, and so on, but I'd like an example of one of the
>>>following please.
>>>"<" Autodecrement addressing memory
>>>">" Autoincrement addressing memory
>>>Thank you.
>>
>>Unfortunately, gcc does not accept ">" and "<" on the x86 (inconsistent 
>>operand constraints in an `asm'). It'll bypass the '<' or '>' if you 
>>specify another constraint with it (Multiple Alternative).
>>Perhaps because there are no implicitly auto-increment or auto-decrement 
>>registers on the x86.
>>
>>If it did accept '<' and '>', then it could cld / std and use ESI for 
>>the output memory operand and EDI for the input memory operand.
> 
> I tried thanking you for your help, but something obviously went wrong
> with the last message I tried posting, so I'm trying this again.  I
> hope it posts OK this time.

Your previous message did get through. 
<84e4e2a9 DOT 0307251553 DOT 4b73681 AT posting DOT google DOT com>

Strange that Google put your Thankyou ("OK, thanks for the info.") in 
the quote.