Hi Duc, Having the print not displayed on screen does not necessarily mean that it has not been executed. It could just have been stuck in stdout buffer which was not flush because of an abnormal program termination.
If you initialize you data with truly random and unbounded data, "number = block.number[i] >> 25" could be as big as (2^(64-25)-1) which is... huge, even taking the sqrt. If you have not already done so, you should check that cap is not to big in some cases and that the program takes a reasonable amount of time when running natively on your host. By reasonable, I mean a couple of ms for a less than a minute simulation on gem5. And as a side note, if you want to stress your caches, you can have a look at the MemTest cpu in gem5. It is purposely built to generate back to back memory accesses with controlled line sharing. Best, Gabriel _______________________________________________ gem5-users mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
