tag:blogger.com,1999:blog-1984932124087943660.post3776667538331992359..comments2019-01-10T17:09:39.079+01:00Comments on Kio's Hardware Projects: Hit the Ceiling – Going VirtualAnonymoushttp://www.blogger.com/profile/17460730281415132574noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1984932124087943660.post-44270078889367973122016-06-02T01:42:03.698+02:002016-06-02T01:42:03.698+02:00A little off-topic here but do you happen to have ...A little off-topic here but do you happen to have some source code made public? I would be interested in testing code size generation with z88dk and perhaps looking at ways the generated code could be improved.<br /><br />You may not be aware but z88dk has its own version of sdcc that currently produces better code than sdcc. I did note in a past blog entry that you found that finding "z88dk_callee" and "z88dk_fastcall" linkages in sdcc was a little odd - well now you know that the two projects have been working together for the past year to give sdcc access to z88dk's library and crts :)<br /><br />The code improvements over plain sdcc derive mainly from bugfixes that have not yet been applied to sdcc, a much larger peephole rule set, and most importanty, a more complete c library written in assembly language. Another contributor that may affect ROM size in particular is that z88dk can produce an lz77-compressed data section that is stored in ROM, rather than a block of raw bytes that are simply ldir'ed into RAM at startup.<br />Anonymoushttps://www.blogger.com/profile/14348849584934687408noreply@blogger.com