This is the mail archive of the
mailing list for the eCos project.
RE: GNU toolchains for eCos 3.0
- From: "Chris Zimman" <czimman at bloomberg dot com>
- To: "Ilija Kocho" <ilijak at siva dot com dot mk>, "eCos discuss list" <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 4 Sep 2008 17:20:06 -0400
- Subject: RE: [ECOS] GNU toolchains for eCos 3.0
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:ecos-discuss-
> email@example.com] On Behalf Of Ilija Kocho
> Sent: Thursday, September 04, 2008 2:39 PM
> To: eCos discuss list
> Subject: Re: [ECOS] GNU toolchains for eCos 3.0
> I think Sergei is not alone.
> Standardized tool-chain is important contribution to eCos' stability. It
> will also facilitate bug hunting by making test cases reproducible.
> I would mention that information on library versions (vxWidgets, Tcl/Tk)
> used for eCos 3.0 configuration tools is also important.
> At the end if it is not decided yet, I would suggest to get some fresh
> GCC release (4.2... or newer).
> Best regards
There isn't anything "magic" that ties eCos to any particular toolchain, etc.
For example, I use CodeSourcery ARM EABI at the moment. If anything, the
newer toolchains have shown places that the code consistency could be
improved (eg. const ness of things). There are sometimes bugs that are
somewhat obscure (eg. the linker coalescing sections that breaks the static
constructor init), but these problems are generally fairly straight forward
to find and to work around.
Just my $.02
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss