I'm not sure what the actual status of the -native flag is, but I know that when I tried to use it a while ago it was also broken and Avadh told me to use kill instead.
If you use -kill or ptlcall_kill(), it should write out the final snapshot. On Fri, Jan 7, 2011 at 11:41 AM, Timothy Hayes <[email protected]> wrote: > Hello > > I've started using MARSS for a research project, my thanks to all of you > involved for a great piece of software. > > I have a question regarding switching between simulated and native modes. I > would like to execute my program in full and wrap the significant kernels in > 'ptlcall_switch_to_sim()' and 'ptlcall_switch_to_native()'. The former works > fine but when I call the latter, MARSS informs: > MARSSx86::Command received : -native > Warning: invalid option '-native' > > I've tried using 'ptlcall_single_flush("-stop")' in lieu of -native, but > when I try to do 'ptlcall_kill()' at the end of the program's execution, > MARSS informs: > MARSSx86::Command received : -kill > Warning: only one action (from -run, -stop, -kill) can be specified at once > > This is problematic as the final snapshot isn't written to my stats file. > Can you advise me the typical way users circumvent this issue? > > Kind regards > Tim > > p.s. this naturally leads me to ask if I can run multiple benchmarks with > different logfiles/stats without having to kill and restart the SUT each > time? > > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
