Correction: it was sufficient for me to include m5op.h properly. Before, the compiler was only finding the function (m5_exit) at link-time, so I suppose that was causing some problem.
On Tue, May 17, 2011 at 1:33 PM, Gedare Bloom <[email protected]> wrote: > Thanks. The problem was that writing to the parameter was optimized > out. I have corrected it locally by adding volatile to the parameter > name in m5op.h. > -Gedare > > On Tue, May 17, 2011 at 12:36 AM, Ali Saidi <[email protected]> wrote: >> You'll have to play a compiler trick to make sure it doesn't optimize out >> the call. You can have it return a value you consume or mark the function in >> the header as volatile. >> >> >> >> Ali >> >> >> >> On Mon, 16 May 2011 23:40:56 -0400, Gedare Bloom <[email protected]> >> wrote: >> >> Hi, >> I put m5_exit in a program and it is not executed under arm_fs. The >> m5_checkpoint that I added works fine. I can make exit work if I put it >> after a printf, but that is not ideal. Any advice? >> -Gedare >> >> >> >> _______________________________________________ >> gem5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> > _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
