Skip to main content
Jump to: navigation, search

DSDP/RTSC - Performance

Revision as of 20:36, 17 February 2010 by (Talk | contribs)


Build time

These benchmarks measure the total time to build an application including the generation of configuration package (which only happens the first time a configuration is created).

BIOS memory example built with BIOS for C64P and MSP430 targets, 'whole_program' profile
XDCtools target generating configPkg rebuilding configPkg big C compile partial link opt compile app build Total C64P 3s 25s 13s 28s 7s 2s 78s C64P 3s 17s 13s 28s 7s 2s 70s C64P ELF 3s 18s 21s 40s 28s 2s 112s (symdebug:none) C64P ELF 3s 18s 11s 23s 4s 2s 61s MSP430 3s 18s 7s 11s 4s 2s 45s
3.20 with -O0 C64P 3s 17s 11s 28s 7s 2s 68s
3.20 with DirectCall C64P 3s 17s 10s 27s 7s 2s 66s
3.20 with DirectCall and -O0 C64P 3s 17s 8s 27s 6s 2s 63s

The last column includes not only -O0, but also -oi0 and --symdebug:none thrown in when compiling the big C config file.

C64P ELF was built with the 7.0.0 tools. There was no difference in C64P COFF build times between 6.1.12 and 7.0.0 tools.

different configurations, XDCtools, 'whole_program' profile
app big C lines modules big C compile time link time
MSP430 local.apps.monitor 8000 18 3s 8s
C64P memory 25000 35 13s 28s
C64P rta 40000 57 24s 55s

Command line tool startup time

These benchmarks measure the time required to start up an java environment, print a message, and shutdown from the command line.

command line tools
XDCtools java tconf xs 0.41s 0.8s 1.3s

Various documents

whole_program build flow diagram

Copyright © Eclipse Foundation, Inc. All Rights Reserved.