From:	"AndrewJ" <luminous-is AT home DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<5337D585DDD3D111996B0008C728F07DA42A4B AT pa00fsr01 DOT pa DOT atitech DOT com> <200007210832 DOT KAA07828 AT mailgw3 DOT netvision DOT net DOT il> <bjsgnsceubs20n5d6b3rl32hvo4ebea0dj AT 4ax DOT com> <200007211841 DOT VAA24548 AT mailgw1 DOT netvision DOT net DOT il>
Subject:	Re: Watcom vs djgpp
Lines:	17
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID:	<4rse5.206152$7o1.5268864@news2.rdc1.on.home.com>
Date:	Sun, 23 Jul 2000 02:06:56 GMT
NNTP-Posting-Host:	24.42.120.18
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news2.rdc1.on.home.com 964318016 24.42.120.18 (Sat, 22 Jul 2000 19:06:56 PDT)
NNTP-Posting-Date:	Sat, 22 Jul 2000 19:06:56 PDT
Organization:	@Home Network Canada
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Gas does support Intel syntax, but it's tricky to make GCC invoke it
> with the appropriate switch.
>
> Anyway, that's not the problem I had in mind.  Watcom has special
> pragmas frequently used with inline assembly, which will need to be
> converted to GCC equivalents.  This is not easy.

The pragma's should be no more difficult to convert than normal _asm {} blocks.
There are a few tricky things to take into consideration, such as the ability
to define what variables go into what registers, instead of having them passed
in Watcom's normal order.  What specifically did you have in mind, Eli?
(Anything pertaining to Watcom C interests me ;)

AndrewJ

- Raw text -