This is the mail archive of the ecos-discuss@sourceware.cygnus.com mailing list for the eCos project. See the eCos home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>>>>> "Paolo" == Paolo Torricelli <ptorric@tsc4.com> writes:
Paolo> i'm considering to port ecos on hitachi h/800
>> The problem is in the toolchain: as I understand it there is no g++
>> support for the h8/300, only gcc support; also ELF object format is
Paolo> At the present i'm using gcc by Cygnus as distributed in
Paolo> Hitachi cd-rom I must understand why Ecos is maded with
Paolo> g++. In my long years of computer activity i know (on my
Paolo> shink) that there is no way to port anything if it isn't
Paolo> maded in simple (and very simple) C. Anyway maybe i can
Paolo> consider to port gnu tools...maybe to adopt another OS.
Paolo> This is not polemic, only a real topic sorry
It is a valid point, and the decision to use C++ for eCos rather than
ISO C was not an easy one. Another controversial decision we made
early on was to tie eCos to the GNU tools, making it very difficult to
use any other compiler technology. C++ is the more powerful language
of the two, even if some aspects of the language such as exception
handling usually cannot be used in an embedded system because of code
size issues.
In terms of availability, these days there are very few toolchains
where gcc is available but not g++ - the extra amount of work involved
is supposedly quite small, although I am not an expert on the
internals of the tools. The h8/300 is the exception rather than the
rule. If there is sufficient demand than either somebody will
contribute the necessary support or some major player (possibly
Hitachi, possibly a company that wants to use the h8 in a big project)
will pay for the work to be done.
Bart Veer // eCos net maintainer