gnupic: gpasm bugs


Previous by date: 25 Mar 2002 21:37:27 -0000 Re: gpasm bugs, Byron A Jeff
Next by date: 25 Mar 2002 21:37:27 -0000 Re: fate of 18F0x0 chips?, John Rehwinkel
Previous in thread: 25 Mar 2002 21:37:27 -0000 Re: gpasm bugs, Byron A Jeff
Next in thread: 25 Mar 2002 21:37:27 -0000 Re: gpasm bugs, Jesse Lackey

Subject: Re: gpasm bugs
From: "Eric Smith" ####@####.####
Date: 25 Mar 2002 21:37:27 -0000
Message-Id: <33237.64.169.63.74.1017091855.squirrel@ruckus.brouhaha.com>

> The assembler treats the second operand of the instruction as a number.
> So as far as it's concerned whatever value RamLocation2 represents is
> the number for the second operand. Also that operand is a single bit,
> so the assember only uses the least significant bit.

There's no reason why the assembler shouldn't consider it an error
if the W/F operand has a value other than 0 or 1.  This would catch
the vast majority of cases where the user tried to use the wrong
kind of operand.




Previous by date: 25 Mar 2002 21:37:27 -0000 Re: gpasm bugs, Byron A Jeff
Next by date: 25 Mar 2002 21:37:27 -0000 Re: fate of 18F0x0 chips?, John Rehwinkel
Previous in thread: 25 Mar 2002 21:37:27 -0000 Re: gpasm bugs, Byron A Jeff
Next in thread: 25 Mar 2002 21:37:27 -0000 Re: gpasm bugs, Jesse Lackey


Powered by ezmlm-browse 0.20.