AW: [Sdcc-user] GPL output ?

[<MSoegtrop@Michael-Soegtrop.de>]

Dear Bodo,

Gcc can produce code for Ubicoms IP2022, which is an 8 bit controller
with a PIC style command set (not binary compatible, but similar
functionality). One extension this processor has to make Gcc happy is
stack pointer relative addressing. Without stack pointer relative
addressing, Gcc can not easily produce efficient code. One way to use
Gcc on machines without stack pointer relative addressing is to declare
many of the internal RAM as CPU-registers in the MD file and use
registers for function parameters. If your code does not use many local
variables, the stack (which has to use dp addressing and is quite
inefficient) is not used much. I played around with the IP2022 MD file a
bit to test what kind of code it can produce this way, and it was not
bad, but SDCC is superior for machines without stack pointer relative
addressing.

Although GCC can not easily compete with SDCC on 8051s, i don't know why
SDCC does not use the GNU binutils (assembler, linker ...). The binutils
are very nice, and i don't see any reason, why it should not be possible
to use them for 8051 and PICs. You can use them for the IP2022 which has
all the oddities of a 8051 like bit variables, multiple addressspaces
and everything. I think it would safe a lot of development work and
result in a more complete and compatible tool chain.

Best regards,

Michael

> -----Urspr=FCngliche Nachricht-----
> Von: sdc...@li...=20
> [mailto:sdc...@li...] Im Auftrag von=20
> Bodo Wenzel
> Gesendet: Samstag, 8. M=E4rz 2003 09:57
> An: sdc...@li...
> Betreff: Re: [Sdcc-user] GPL output ?
>=20
>=20
> Just my 0.02 EUR:
>=20
> Compilers under GPL (with no additions!) produce code for any=20
> license you=20
> like, including closed. In general, tools under GPL don't=20
> force you to put=20
> their output under GPL.
>=20
> GCC's targets are at least 16 bit CPUs, eventhough I heard=20
> about the Atmel=20
> RISC port. AFAIK GCC can't compile for 8051, Z80, 6502, PIC,=20
> ... I'd love to=20
> be proven false!
>=20
> SDCC's targets are small devices, hence the name...
>=20
> So SDCC and GCC live in completely different worlds.
>=20
> Bodo
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of=20
> TotalView, The debugger=20
> for complex code. Debugging C/C++ programs can leave you=20
> feeling lost and=20
> disoriented. TotalView can help you find your way. Available=20
> on major UNIX=20
> and Linux platforms. Try it free. www.etnus.com=20
> _______________________________________________
> Sdcc-user mailing list
> Sdc...@li...=20
> https://lists.sourceforge.net/lists/listinfo/s> dcc-user
>=20