Hi, I can confirm your bug. The problem happened between
the commits: 81db5ccf3c41e28966ce547e3fd783634581a077 and fe7304ca1e834c67484b52fd180efad0027bbca5 I have further to investigate whats going wrong. If you checkout the last commit, It should work. Regards Matthias > Am 10.08.2017 um 01:57 schrieb hidayatullah chowdary > <chowdaryhidayatul...@gmail.com>: > > Hi, > > I am having trouble in running trace based simulation. Non trace simulation > is running fine. > > This is the command that I have used - > build/X86/gem5.opt configs/example/se.py --elastic-trace-en > --data-trace-file=deptrace --inst-trace-file=fetchtrace --cpu-type=DerivO3CPU > --l1d_size=64kB --l1i_size=16kB --mem-type=SimpleMemory -c ../queens -o 8 > --caches --sys-clock=1GHz > > Error I got is: > **** REAL SIMULATION **** > info: Entering event queue @ 0. Starting simulation... > gem5.opt: build/X86/cpu/o3/probe/elastic_trace.cc:733: void > ElasticTrace::compDelayPhysRegDep(ElasticTrace::TraceInfo*, > ElasticTrace::TraceInfo*): Assertion `execution_tick >= completion_tick' > failed. > Program aborted at tick 397000 > --- BEGIN LIBC BACKTRACE --- > build/X86/gem5.opt(_Z15print_backtracev+0x15)[0x1398755] > build/X86/gem5.opt(_Z12abortHandleri+0x39)[0x13a3909] > > > Unable to understand what is the error here, is there some problem with > setting of execution time? > > Regards > Hidayat > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users _______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users