From: Philipp K. K. <pk...@sp...> - 2009-09-27 11:09:17
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I suggest to remove the avr port from sdcc. - -The port is currently unmaintained - -There exists another, better free copiler for avr (gcc) - -avr has a large number of general purpose registers; one of sdcc's strength lies in being able to generate code for architectures with only a small number of registers, special purpose register among them (unlike gcc which tends to need many general purpose registers to works well) In case you agree about this, we'd ask on sdcc-users about this. If we don't find users of the avr port we could then remove it. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkq/RMwACgkQbtUV+xsoLpopnQCgm1B5gTuqlc4Ik7kwwL98ip3J TDEAn0H1urI9MFEqQu/JsJOsvODNDqX0 =WwVE -----END PGP SIGNATURE----- |
From: Maarten B. <sou...@ds...> - 2009-09-27 13:05:13
|
I'm ok with that. And while we're at it we could also question those other unmaintained remnants: izt and xa51. Esp. izt (intel 186) is very odd for SDCC and supported by other compilers (e.g. OpenWatcom). Maarten > I suggest to remove the avr port from sdcc. > > - -The port is currently unmaintained > - -There exists another, better free copiler for avr (gcc) > - -avr has a large number of general purpose registers; one of sdcc's > strength lies in being able to generate code for architectures with only > a small number of registers, special purpose register among them (unlike > gcc which tends to need many general purpose registers to works well) > > In case you agree about this, we'd ask on sdcc-users about this. If we > don't find users of the avr port we could then remove it. > > Philipp |
From: Philipp K. K. <pk...@sp...> - 2009-09-27 14:08:04
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Maarten Brock schrieb: > I'm ok with that. And while we're at it we could also > question those other unmaintained remnants: izt and > xa51. Esp. izt (intel 186) is very odd for SDCC and > supported by other compilers (e.g. OpenWatcom). Do these ports still fullfill a purpose, i.e. are in some way better than other compilers out there? Are there free compilers for xa51 and i186? OpenWatcom is of dubious freeness: Debian does not consider it free. There are some strange things in the license. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkq/bCEACgkQbtUV+xsoLpqLXgCfXJmpPs+fHEvGCQBkH4Z+JWZx QWMAnR2L7TbjyeMkBj6e12Hn+9a0FxZ/ =/qW3 -----END PGP SIGNATURE----- |
From: Michael H. <mic...@ju...> - 2009-09-27 20:30:47
|
I never finished the itz port - that was back when I had a NeoGeo Pocket with the Toshiba 16 bit version of the Z80 and was interested in the i186 as well. The Z80, Toshiba, and i186 are all architecturally similar so I thought I could do a combined port. I say delete it. -- Michael 2009/9/28 Philipp Klaus Krause <pk...@sp...>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Maarten Brock schrieb: >> I'm ok with that. And while we're at it we could also >> question those other unmaintained remnants: izt and >> xa51. Esp. izt (intel 186) is very odd for SDCC and >> supported by other compilers (e.g. OpenWatcom). > > Do these ports still fullfill a purpose, i.e. are in some way better > than other compilers out there? Are there free compilers for xa51 and > i186? OpenWatcom is of dubious freeness: Debian does not consider it > free. There are some strange things in the license. > > Philipp > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkq/bCEACgkQbtUV+xsoLpqLXgCfXJmpPs+fHEvGCQBkH4Z+JWZx > QWMAnR2L7TbjyeMkBj6e12Hn+9a0FxZ/ > =/qW3 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Philipp K. K. <pk...@sp...> - 2009-09-29 21:17:09
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Hope schrieb: > I never finished the itz port Does that mean it's unusable? Or does it just generate rather unoptimized code? Phiilpp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrCdkUACgkQbtUV+xsoLprvUgCff/bVfoiW9yQ6ciL9nSTqM/rv hQMAoJGm7Zw1dHwDURsJLXnxGhMHUjo1 =/sfI -----END PGP SIGNATURE----- |
From: Michael H. <mic...@ju...> - 2009-09-29 22:13:39
|
It's not usable. I don't think it even generates basic code. -- Michael 2009/9/30 Philipp Klaus Krause <pk...@sp...>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Michael Hope schrieb: >> I never finished the itz port > > Does that mean it's unusable? Or does it just generate rather > unoptimized code? > > Phiilpp > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkrCdkUACgkQbtUV+xsoLprvUgCff/bVfoiW9yQ6ciL9nSTqM/rv > hQMAoJGm7Zw1dHwDURsJLXnxGhMHUjo1 > =/sfI > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > |
From: Philipp K. K. <pk...@sp...> - 2009-09-30 06:44:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Hope schrieb: > It's not usable. I don't think it even generates basic code. OK. So it probably doen't make sense to keep that one. Michael proposed another port for removal, the xa51. When I try to use it, even for an empty function, it just crashes. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrC/kQACgkQbtUV+xsoLpp3hACg2sopYf6dlKeSy3qajcvia3Rk G10AnRogJc3M/Z3m9/ZX9eHKckirqfjQ =LIQH -----END PGP SIGNATURE----- |
From: Borut R. <bor...@si...> - 2009-10-04 14:53:08
|
I think we have to define what "remove port" ("remove target" would be more accurate) means: - remove it from the sdcc build or - remove it from subversion source control The xa51 and avr targets are currently included in the sdcc build while izt target is not. I agree to remove xa51 and avr targets from the sdcc build. I'm not sure whether to remove them from source control or not: using svn history they can be restored if needed in the future anyway... Borut Philipp Klaus Krause wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Michael Hope schrieb: > >> It's not usable. I don't think it even generates basic code. >> > > OK. So it probably doen't make sense to keep that one. > > Michael proposed another port for removal, the xa51. > When I try to use it, even for an empty function, it just crashes. > > Philipp > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkrC/kQACgkQbtUV+xsoLpp3hACg2sopYf6dlKeSy3qajcvia3Rk > G10AnRogJc3M/Z3m9/ZX9eHKckirqfjQ > =LIQH > -----END PGP SIGNATURE----- > |