gnupic: Re: [gnupic] Possible gpasm or gplink bug?
Subject:
RE: [gnupic] Possible gpasm or gplink bug?
From:
Chen Xiao Fan ####@####.####
Date:
15 Nov 2005 07:11:03 +0000
Message-Id: <3B8AEFFADD3DD4118F8100508BACEC2C0A2893AE@spex>
>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.
I tried the same example using gpasm/gputils, gpasm/gputils
produce the correct results just like MPASM/MPLINK.
...
UDATA_SHR
WTEMP res 1 ; register used in Interrupt Routine
...
movlw WTEMP -->
...
00007d 3025 MOVLW 0x25 movlw WTEMP (for MPASM/MPLINK)
00007d 3020 movlw 0x20 movlw WTEMP (for gputils)
Maybe Julian could post more details. A wild guess
is that the RAM address is running out.
Regards,
Xiaofan
