c - Running time vary on Microblaze after code modification -
when modifications in code runs on microblaze, see large discrepancy in runtime execution of code follows same path. illustrate, mean same path, take example,
if ( condition ) execute_this(); else execute_that(); // modified function
so if modified code function execute_that
, see change in runtime when condition
set , function execute_this
has not been modified. can cause this? memory alignment of functions? cache? clue?
does timing only change when change other function, or variable anyway?
are running os? other tasks pre-empt yours?
are interrupts running? interrupt during function change runtime.
and, yes, cache effects could cause this.
Comments
Post a Comment