Re: [sdcc-devel] Questions about z80 port, and maybe pic port too...

[Jesus Calvino-F. <Je...@ec...>]

Hi Michael,

Already done points 1) and 2).  Regarding point 2) the problem with the 
command line is that it may overflow the command line input of some OSs, so 
now the z80 link execution is similar to that of the mcs51 port.

Regarding the Z80 port, is it float/long support functional?  sdccman.lyx 
says somewhere that it isn't...

Jesus

At 05:53 PM 7/13/2003 +1200, you wrote:
>On Friday, July 11, 2003, at 02:38 PM, Jesus Calvino-Fraga wrote:
>
>>Hi all,
>>
>>Recently I have been playing with the z80 port of SDCC.  Maybe somebody 
>>can help me with this doubts:
>>
>>1) The assembler generated files seen to have a lot of 8051 related stuff 
>>on them.  Would it be save to skip the creation of things like bits, sfr, 
>>xdata, etc. so the z80 assembly file looks cleaner and more meaningful?
>
>Yip, please do.
>
>>2) The linker is called with command line options instead of using a .lnk 
>>file as in the 8051 port.  In fact a 8051 lnk file is generated for the 
>>z80 port, which of course is useless unless the right commands are passed 
>>to the linker.  Wouldn't it be more convenient to use a lnk file?
>
>Coming from a Unix background, I much prefer everything to be on the 
>command line rather than using an intermediate file.  The z80 is also a 
>very simple target and doesn't require the linking complexity that some 
>devices do.
>
>>3) The z80 port seems to be using just one library: z80.lib.  What about 
>>using the same libraries as in the 8051 port?
>
>It should be using the same standard library code as all of the other 
>ports with a set of z80 specific extensions from the device/lib/z80 
>directory.  Would you mind checking the linker commands?  There should be 
>two library directories referenced matching the two described above.
>
>-- Michael