gnupic: gpasm question/may be a bug


Previous by date: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Tobias Schlottke
Next by date: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Craig Franklin
Previous in thread: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Tobias Schlottke
Next in thread: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Craig Franklin

Subject: Re: gpasm question/may be a bug
From: Samuel Tardieu ####@####.####
Date: 18 Oct 2002 21:05:00 -0000
Message-Id: <2002-10-18-23-01-40+trackit+sam@rfc1149.net>

Tobias> Ok, but if it _has_ to be f or w, at least a warning would be
Tobias> nice to have. I.E. if I write bsf 0x20,8 the compiler
Tobias> generates a warning that 8 is out of range.  I feel xorwf
Tobias> PORTB,PORTB easier to read, even if the second argument must
Tobias> be the same like the first one (or equal w).

In this case, "xorwf INDF,INDF" looks clearer than "xorwf INDF,f", but
will be incorrectly compiled as "xorwf INDF,w" as "INDF" is zero :)

Tobias> ok, if you know how the assembler is implemented, then there
Tobias> is no mistery.

I don't; I only looked at the datasheet.

  Sam
-- 
Samuel Tardieu -- ####@####.#### -- http://www.rfc1149.net/sam


Previous by date: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Tobias Schlottke
Next by date: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Craig Franklin
Previous in thread: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Tobias Schlottke
Next in thread: 18 Oct 2002 21:05:00 -0000 Re: gpasm question/may be a bug, Craig Franklin


Powered by ezmlm-browse 0.20.