From:	"Fairbairn Family" <lgcl01 AT es DOT co DOT nz>
Newsgroups:	comp.os.msdos.djgpp
Subject:	ARGH! ....... Its always a simple bug ........
Date:	Sun, 26 Nov 2000 00:39:56 +1300
Organization:	ihug ( New Zealand )
Lines:	30
Message-ID:	<8vo8rj$1k2$1@lust.ihug.co.nz>
References:	<8vn57g$rol$1 AT lust DOT ihug DOT co DOT nz> <8vnig9$5sl$2 AT newsg1 DOT svr DOT pol DOT co DOT uk> <8vo4e9$m95$1 AT lust DOT ihug DOT co DOT nz>
NNTP-Posting-Host:	p47-max1.inv.ihug.co.nz
X-Trace:	lust.ihug.co.nz 975152820 1666 203.173.222.175 (25 Nov 2000 11:47:00 GMT)
X-Complaints-To:	abuse AT ihug DOT co DOT nz
NNTP-Posting-Date:	Sat, 25 Nov 2000 11:47:00 +0000 (UTC)
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
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,

I think I have it sorted out now.....

My conversion between Intel and AT&T syntax was not 100% correct... The AS
input file contained the following extract:
> kisypp_signon:
>     .ascii "Hello world! This is GAS\n$"
<snip>
>     movw kisypp_signon,%dx
>     call put_string

The line movw kisypp_signon,%dx

should have been

movw $kisypp_signon,%dx

I noticed that after finding an x86 disassembler after disassembling both
object files.

With that gramatical change the com file produced via AS has the same output
(bar the padding) as the one assembled with NASM. The only other difference
in the COM files from the 2 sources shown is that AS used a jump short while
NASM used a jump (resulting in the first difference shown).

Thanks for all your help,
Christopher

- Raw text -