On 11/11/2011 02:46 PM, Butuza Tamas wrote:
> Dear sdcc developers,
> I cannot buid sdcc and gputils from source, therefore I could use precompiled binaries for testing.
Which platform (operating system) are you using? I'll prepare the
gputils from the svn head for you.
> These are a bit older than the actual svn heads. I used these versions:
> sdcc: 3.1.0 #7019
> I used PIC16F1938 with PIC16F1936 headers (there is no header and inc for 16F1938 in the mentioned versions)
> I could not link with libsdcc.lib because a processor family mismatch. As I know it is fixed already in svn.
> However, it is possible to work without this lib.
Raphael commited sdcc enh. 14 bit devices support, so it should work
with the todays sdcc snapshot.
> The resulted code is working properly in the pic.
Geat! But please repeat the test with the todays sdcc snapshot (this is
planned to be the RC2) and with the svn head gputils version I'll
prepare for you.
> I realized, that gpdasm does not recognize the MOVLB instruction (0x02x)
This should be fixed in the svn head.
> Config values at 0x8007 and 0x8008 interpreted as code.
> Maybe it is already fixed in svn head.
Disassembler doesn't distinguish between the code and date, so it first
tries do disassemble and if it fails it assumes that it is data. This
could be fixed in cases where we can distinguish between code and data,
but it is a low priority task. You can fill a gputils enhancement request.
> Other recommendation:
> Sdcc generates a startup function to initialize data in ram. (copy values from rom to ram)
> This feature should be able to switch off when it is not necessary. It could be useful for low memory microcontrollers.
This is an enhancement request for sdcc project. Please submit it.
Thanks for testing,