This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

A basic question regarding [eCos] performance figures


when one cites various eCos performance figures
related to footprint and timings for core functions
(as printed via tm_basic tests) --

are those generated using certain compiler flags (like
-O2, -Os etc.) applied during compilation and some
linker flags for relaxation pass etc. during linking -
to reduce code size and also have impact on execution
timings.

also i would like to seek opinions of experts on - 
is there any issue with the process of code-tweaking
that is tied down to how the toolchain in question
generates code with particular compiler flags, though
this way it generates tighter object code, that would
improve code size and speed? this kind of things can't
be done for common code though.

sure, this might at times, render the source code, not
easily comprehensible. but should this matter to me as
a user, if i am not given the source code, just the
binaries and needed headers.

regards
sandeep




		
_______________________________
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now. 
http://messenger.yahoo.com

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]