Does it make sense to use m5.fast or m5.debug? On 2/15/12, Steve Reinhardt <[email protected]> wrote: > "--trace-flags" is obsolete, it's been replaced by "--debug-flags" > > Jack is suggesting that you run the commands manually just to verify that > they are correct and generating output before you try to use them with > tracediff. > > Tracediff runs two different commands at the same time and compares their > output, so it won't work to compare runs where you make the change by > directly editing a config file, since you can't have two different versions > of the same file with the same name at the same time. You have to expose > the thing you want to change as a command-line parameter, rename one of the > config files, run in two separate clones of the source tree, or something > like that. > > Steve > > On Wed, Feb 15, 2012 at 3:52 AM, Mahmood Naderan > <[email protected]>wrote: > >> the two commands are: >> >> -build/X86_SE/m5.debug -d tracediff-5552-1 >> --trace-flags=Exec,-ExecTicks configs/example/cmp.py -F 500000000 >> --maxtick 1000000000000 --caches --l2cache --l2size 4MB -b cactus 2>&1 >> | >> +build/X86_SE/m5.debug -d tracediff-5552-2 >> --trace-flags=Exec,-ExecTicks configs/example/cmp.py -F 500000000 >> --maxtick 1000000000000 --caches --l2cache --l2size 2MB -b cactus 2>&1 >> | >> >> >> You mean that I must manually execute then and the manually compare >> the trace files. Right? >> >> What is the power of tracediff then? It only generate the commands? >> >> On 2/15/12, Jack Harvard <[email protected]> wrote: >> > The warning message is due to not using "--debug-flags", as you used >> > "--trace-flags". You can just run one of the two commands being >> > generated, and see what happens, just to make sure all the options are >> > correctly applied. >> > >> > Jack Harvard >> > >> > On Wed, Feb 15, 2012 at 10:14 AM, Mahmood Naderan <[email protected]> >> > wrote: >> >> Well I tried something but see no result: >> >> >> >> mahmood@tu1:gem5$ util/tracediff build/X86_SE/m5.debug >> >> --trace-flags="Exec,-ExecTicks" configs/example/cmp.py -F 500000000 >> >> --maxtick 1000000000000 --caches --l2cache "--l2size 4MB|--l2size 2MB" >> >> -b cactus >> >> **** >> >> **** WARNING: no debug flags set... you may not be diffing much! >> >> **** >> >> Executing /home/mahmood/gem5/util/rundiff 'build/X86_SE/m5.debug -d >> >> tracediff-5552-1 --trace-flags=Exec,-ExecTicks configs/example/cmp.py >> >> -F 500000000 --maxtick 1000000000000 --caches --l2cache --l2size 4MB >> >> -b cactus 2>&1 |' 'build/X86_SE/m5.debug -d tracediff-5552-2 >> >> --trace-flags=Exec,-ExecTicks configs/example/cmp.py -F 500000000 >> >> --maxtick 1000000000000 --caches --l2cache --l2size 2MB -b cactus 2>&1 >> >> |' 2>&1 > tracediff-5552.out >> >> >> >> >> >> Immediately the execution ends. There are no files in >> >> tracediff-5552-1/ and tracediff-5552-2/ >> >> >> >> What is wrong with that? >> >> >> >> On 2/15/12, Jack Harvard <[email protected]> wrote: >> >>> Tracediff is a small perl script, ./util/tracediff, have a look at the >> >>> file directly, that should answer your question. >> >>> >> >>> Jack Harvard >> >>> >> >>> On Tue, Feb 14, 2012 at 3:10 PM, Mahmood Naderan <[email protected] >> > >> >>> wrote: >> >>>> Hi >> >>>> How can I use tracediff? The document at >> >>>> http://gem5.org/Debugging#tracediff is not very clear. >> >>>> >> >>>> Consider I want to run two simulations with different cache size. The >> >>>> benchmark and instructions are equal. Normal steps are: >> >>>> >> >>>> 1- chanage L2Cache size to 2MB in common/Caches.py >> >>>> 2- run build/X86_SE/m5.fast configs/example/cmp.py --caches --l2cache >> -b >> >>>> gcc >> >>>> 3- chanage L2Cache size to 512kB in common/Caches.py >> >>>> 4- run build/X86_SE/m5.fast configs/example/cmp.py --caches --l2cache >> -b >> >>>> gcc >> >>>> >> >>>> seems that tracediff only works when command lines change. Is that >> >>>> right? >> >>>> -- >> >>>> // Naderan *Mahmood; >> >>>> _______________________________________________ >> >>>> 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 >> >>> >> >> >> >> >> >> -- >> >> -- >> >> // Naderan *Mahmood; >> >> _______________________________________________ >> >> 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 >> > >> >> >> -- >> -- >> // Naderan *Mahmood; >> _______________________________________________ >> gem5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >
-- -- // Naderan *Mahmood; _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
