Message-ID:	<326C8392.14F8@gbrmpa.gov.au>
Date:	Tue, 22 Oct 1996 16:19:35 +0800
From:	Leath Muller <leathm AT gbrmpa DOT gov DOT au>
Reply-To:	leathm AT gbrmpa DOT gov DOT au
Organization:	Great Barrier Reef Marine Park Authority
MIME-Version:	1.0
To:	ivie AT cc DOT usu DOT edu
CC:	djgpp AT delorie DOT com
Subject:	Re: porting watcom progs
References:	<32628507 DOT 3B61824 AT mercury DOT execulink DOT com> <slrn56n1qg DOT i91 DOT rivie AT intergate DOT daautah DOT com>

Roger Ivie (a known boogerhead) wrote:
> 
> In article <32628507 DOT 3B61824 AT mercury DOT execulink DOT com>, Jeff Weeks wrote:
> [[[ snip ]]]
> >parm [ebx] [cx] [al]\
> >value [ebx]\
> >modify exact [ax cx ebx] nomemory;
> >
> >Most of the code should just be a switch from Intel to AT&T asm right?
> >But what about the three lines at the end?  What are they all about (the
> >parm, value and modify lines)?  And how to I convert those to DJGPP V2
> >assembly.
 
> I do lots of work with Watcom, so I can tell you about those three
> lines. I can't tell you how to convert them to DJGPP V2, though.
 
> These lines tell the Watcom compiler about the register usage of the
> procedure. It takes parameter #1 in ebx, parameter #2 in cx, and
> paramter #3 in al. It returns its value in ebx. It modifies only registers
> ax, cx, and ebx and does not touch memory.

Basically, AT&T style is almost exactly the same. Check the info docs,
or look at brennans page on AT&T assembly (I thinks its something like:
http://www.rt66.com/~brennan). This should tell you everything you need
to know...

Leathal.

- Raw text -