Hi,
Thank you! I completed that project with remaining benchmarks.
On Sat 5 May, 2018, 5:02 AM TungHoang_GMail,
wrote:
> For x264, you need to recompile hooks library with following command
>
> parsecmgmt -a build -c gcc-hooks -p hooks
>
>
___
gem5-us
For x264, you need to recompile hooks library with following command
parsecmgmt -a build -c gcc-hooks -p hooks
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
Moreover, it seems only happening to multi-processes benchmarks since that
my other multithreading benchmarks doesn't have this issue so far.
On Fri, May 4, 2018 at 4:37 PM, Da Zhang wrote:
> Hey guys,
>
> My gem5 real simulation crashed with
> "
>
> gem5.opt: build_alter/build/X86/cpu/timebuf.h
Hey guys,
My gem5 real simulation crashed with
"
gem5.opt: build_alter/build/X86/cpu/timebuf.hh:54: void
TimeBuffer::valid(int) const [with T = DefaultIEWDefaultCommit]:
Assertion `idx >= -past && idx <= future' failed.
"
I am using DerivO3CPU and 4MB l2 cache 32GB mem and ramulator memory.
Resto
Hi Avais,
You might need to remove the snoop filter from the system as well, depending on
what exactly you want to do. Doing so will increase significantly the number of
snoops in the system. But in your case, the snoop filter performs sanity checks
about the coherence protocol and if these che
Dear Nikos,
I have seen that we can bypass snoopfilter in "coherent_xbar.cc"
file by passing snoopfilter variabels as nullptr.
Is it good solution to avoid snoopfilter checking, if we do not care about
coherence protocols in simulation.
Best Regards,
Thanks,
Avais
On Fri, May 4, 2018 a
Hi Muhammad, you are more likely to get answers by following these bug
report recommendations:
https://github.com/cirosantilli-work/gem5-issues/issues/7
On Fri, May 4, 2018 at 8:32 AM, Muhammad Avais wrote:
> Dear All,
>
> Can anyone suggest what this error message indicates
>
> read error, exit
Dear All,
Can anyone suggest what this error message indicates
read error, exit
Exiting @ tick 104585181462 because exiting with last active thread context
And how can i do to debug it?
Many thanks,
Avais
___
gem5-users mailing list
gem5-users@gem5.o