From: Michael W. <m_w...@ho...> - 2005-12-16 23:14:07
|
I'm interested in contributing back to the open source world, and would like to create a port to the Rabbit 3000. I've read the section: "SDCC Docs: 8.4 Retargetting for other Processors", which is nice but stipulates: "The issues ... are far too numerous to be covered by this document". I've also seen interest from Karl Bongers and others, and looked at Stephen Hardy's z2k tool suite, but it seems never to have been brought to a full C compiler. The Rabbit Users' Manual has some pretty good documentation on the likeness and differences from their processor and instruction set to that of the Z80, but I'm stuck at where exactly I should begin. If you could point me in the right direction I'd like to be of help. Are there any other docs that deal with this? Any experienced porters that wants to take me under their wing would be a help. |
From: Michael H. <mic...@ju...> - 2005-12-21 00:35:42
|
Hi Michael. I've had a look at the Z80 differences section in the Rabbit 2000 manual, and the short answer is that sdcc doesn't use any of the instructions removed or changed by the Rabbit designers. You should be able to run programs compiled by sdcc directly on the Rabbit. The next step would be to make use of the extra and enhanced instructions - probably by making a run-time derivative of the z80 code generator z80/gen.c. -- Michael On 17/12/2005, at 12:13 PM, Michael Watchorn wrote: > I'm interested in contributing back to the open source world, and > would like to create a port to the Rabbit 3000. I've read the section: > "SDCC Docs: 8.4 Retargetting for other Processors", which is nice but > stipulates: "The issues ... are far too numerous to be covered by this > document". I've also seen interest from Karl Bongers and others, and > looked at Stephen Hardy's z2k tool suite, but it seems never to have > been brought to a full C compiler. > > The Rabbit Users' Manual has some pretty good documentation on the > likeness and differences from their processor and instruction set to > that of the Z80, but I'm stuck at where exactly I should begin. If you > could point me in the right direction I'd like to be of help. Are > there any other docs that deal with this? Any experienced porters that > wants to take me under their wing would be a help. > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > |
From: Jonathan D. <jdu...@ci...> - 2005-12-21 19:45:53
|
did you look at this project. It's now recent but can have a good starting point. http://rabbitdev.sourceforge.net/ Jonathan ----- Original Message ----- From: "Michael Hope" <mic...@ju...> To: <sdc...@li...> Sent: Tuesday, December 20, 2005 7:35 PM Subject: Re: [Sdcc-user] port of Z80 to Rabbit > Hi Michael. I've had a look at the Z80 differences section in the Rabbit > 2000 manual, and the short answer is that sdcc doesn't use any of the > instructions removed or changed by the Rabbit designers. > > You should be able to run programs compiled by sdcc directly on the > Rabbit. The next step would be to make use of the extra and enhanced > instructions - probably by making a run-time derivative of the z80 code > generator z80/gen.c. > > -- Michael > > On 17/12/2005, at 12:13 PM, Michael Watchorn wrote: > >> I'm interested in contributing back to the open source world, and would >> like to create a port to the Rabbit 3000. I've read the section: "SDCC >> Docs: 8.4 Retargetting for other Processors", which is nice but >> stipulates: "The issues ... are far too numerous to be covered by this >> document". I've also seen interest from Karl Bongers and others, and >> looked at Stephen Hardy's z2k tool suite, but it seems never to have been >> brought to a full C compiler. >> >> The Rabbit Users' Manual has some pretty good documentation on the >> likeness and differences from their processor and instruction set to that >> of the Z80, but I'm stuck at where exactly I should begin. If you could >> point me in the right direction I'd like to be of help. Are there any >> other docs that deal with this? Any experienced porters that wants to >> take me under their wing would be a help. >> >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log >> files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> _______________________________________________ >> Sdcc-user mailing list >> Sdc...@li... >> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > |
From: Philipp K. K. <pk...@sp...> - 2005-12-31 20:13:43
|
Michael Hope schrieb: > Hi Michael. I've had a look at the Z80 differences section in the > Rabbit 2000 manual, and the short answer is that sdcc doesn't use any of > the instructions removed or changed by the Rabbit designers. > > You should be able to run programs compiled by sdcc directly on the > Rabbit. The next step would be to make use of the extra and enhanced > instructions - probably by making a run-time derivative of the z80 code > generator z80/gen.c. Since the additions don't seem to be that important I rather suggest improving the generic Z80 port - there is still a lot of room for optimizations and it requires bug fixes. Philipp |