gnupic: Re: [gnupic] Possible gpasm or gplink bug?


Previous by date: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan
Next by date: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan
Previous in thread: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan
Next in thread: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan

Subject: RE: [gnupic] Possible gpasm or gplink bug?
From: Chen Xiao Fan ####@####.####
Date: 14 Nov 2005 09:31:58 +0000
Message-Id: <3B8AEFFADD3DD4118F8100508BACEC2C0A2893AA@spex>

>...
>In my opinion, Julian's example typifies a general problem with
>relocatable code; RAM variable addresses can't be accessed at assembly
>time. 
>...
>Scott

Hi Scott,

I just tried one simple example and MPASM/MPLINK is okay with 
Julian's method. RAM variable address is resolved correctly
at link time even though it is not availabe at the assemble
pass. 

So Julian may be correct that this is a bug with gpasm/gplink.

Regards,
Xiaofan

...
	UDATA_SHR
WTEMP		res 1	; register used in Interrupt Routine
...
movlw WTEMP --> 
...

00007d 3025 MOVLW 0x25 movlw	WTEMP 

Previous by date: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan
Next by date: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan
Previous in thread: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan
Next in thread: 14 Nov 2005 09:31:58 +0000 Re: [gnupic] Possible gpasm or gplink bug?, Chen Xiao Fan


Powered by ezmlm-browse 0.20.