From:	jbs30000 AT aol DOT com (Joel)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: One final inline assembly constraint question.
Date:	25 Jul 2003 16:53:48 -0700
Organization:	http://groups.google.com/
Lines:	18
Message-ID:	<84e4e2a9.0307251553.4b73681@posting.google.com>
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>
NNTP-Posting-Host:	172.170.32.34
X-Trace:	posting.google.com 1059177228 7584 127.0.0.1 (25 Jul 2003 23:53:48 GMT)
X-Complaints-To:	groups-abuse AT google DOT com
NNTP-Posting-Date:	25 Jul 2003 23:53:48 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

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.
OK, thanks for the info.

- Raw text -