RE: [ECOS] TCP/IP performance under eCos & other compilers than gnu

[Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>]

> -----Original Message-----
> From: Richard Wicks [mailto:rich@accetnetwork.com]
> 
> I'm assuming this is a problem with the gcc compiler and not 
> the BSD stack or 
> the driver.  Although gcc is a fine compiler for x86 and 
> other more common 
> processors, I can see the code it produces for the ARM is 
> less than stellar 
> as it does not take advantage of the ARM's conditional 
> execution architecture 
> very well.


I agree at least for size, according to my own observations gcc produce 10%
more codes than ArmCC (in "release" mode ie with "-02", in "debug" mode - ie
"-g" - it's worth: gcc produce 50% more code than armcc)

> Had anybody compiled eCos (successfully) with another 
> compiler other than 
> gnu?  I'd like to look into using another compiler and I need a 
> recommendation.

I don't think it would be possible since ecos rely on special gcc features.
Plus you will probably have to rewrite the assembly code.  But maybe it's
possible just to use another compiler for the part that can use it and keep
gcc for the assembly code and the code that require special gcc features. 
 
When it's size that matters at least you can compile your own app with armcc
then link it with ecos library. If your app is much bigger than the ecos
kernel, you win.


-- 
Fabrice Gautier
Software Engineer, Sigma Designs
Fabrice_Gautier@sdesigns.com