Re: Different hex file generated by gpasm and mpasm

----- Original Message ----------
On Tuesday 20 September 2005 01:11, Chen Xiao Fan wrote:

> The file in question is a single relocatable assembly
> file and I do not expect too much difference in the
> generated assmebly. Since both are working in the final
> application, both must be correct. Still I am just
> a bit curious what is the difference between gpasm
> and MPASM.

One is open source,the other isn't.

As far as I understand, some consideration has been made to keep the syntax 
for gputils the same or at least similar to mpasm. As a result the operation 
of the application should be broadly the same, however gputils is not a 
cloned implementation of mpasm (this assumes the logic used during 
compilation doesn't change between revisions).

There is more than one way to get the approximately the same point. For 
example, could you tell the difference between these two blocks of code once 
compiled and running?:

1)
int main(){
	char i = 0;
	while(i<10){
		print("%d",i);
		i++;
	}
	return(0);
}

2)
int main(){
	char i;
	for(i=0,i<10,i++){
		print("%d",i);
	}
	return(0);
}

> -----Original Message-----
> From: Peter Onion
> Sent: Tuesday, September 20, 2005 1:56 AM
>
> > Still I have one question, the hex files generated by
> > MPASM and gputils are really different in one test assembly
> > file even though the programmed chips are both working.
>
> I'm curious as to why do you think this a problem ?  Do you often look
> at the hex files ?
>
> Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]

-- 
Martyn Welch ([email protected])

PGP Key : http://ubicomp.lancs.ac.uk/~martyn/pgpkey.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBDL9X3QPzYXciChNcRAlUlAJ9nx77eMre/AHl4joFVJt5ZuQbxygCcD3ki
vyaT/YVTXNDYdtByohEoyTo=
=CaMz
-----END PGP SIGNATURE-----