29.01.2015 Views

Embedded Software for SoC - Grupo de Mecatrônica EESC/USP

Embedded Software for SoC - Grupo de Mecatrônica EESC/USP

Embedded Software for SoC - Grupo de Mecatrônica EESC/USP

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

170 Chapter 13<br />

// Create a chain named “recover” and add three functions<br />

#makechain recover<br />

#funcchain recover free_memory<br />

#funcchain recover <strong>de</strong>clare_memory<br />

#funcchain recover initialize<br />

// Invoke all three functions in the chain in some sequence<br />

recover();<br />

5. PORTING AND DEVELOPMENT ISSUES<br />

A program rarely runs unchanged on a dramatically different plat<strong>for</strong>m; something<br />

always has to change. The fundamental question is, then, how much<br />

must be changed or rewritten, and how difficult these rewrites will be.<br />

We encountered three broad classes of porting problems that <strong>de</strong>man<strong>de</strong>d<br />

co<strong>de</strong> rewrites. The first, and most common, was the absence of certain libraries<br />

and operating system facilities. This ranged from fairly simple (e.g., Dynamic<br />

C does not provi<strong>de</strong> the standard random function), to fairly difficult (e.g., the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!