On Wed, Aug 11, 2021 at 7:20 AM Deric Cheung via gem5-users <
gem5-users@gem5.org> wrote:
> I implemented that patch (
> https://gem5-review.googlesource.com/c/public/gem5/+/49183) and now the
> panic in static_inst.cc no longer occurs. Thank you!
>
> However I still encounter a failed assertion (
https://gem5-review.googlesource.com/c/public/gem5/+/49203
On Thu, Aug 12, 2021 at 4:56 AM Gabe Black wrote:
>
>
> On Wed, Aug 11, 2021 at 7:20 AM Deric Cheung via gem5-users <
> gem5-users@gem5.org> wrote:
>
>> I implemented that patch (
>> https://gem5-review.googlesource.com/c/public/gem5/+/4
Hello all,
I am using MESI Two-level protocol on top of the Garnet network. I want to
calculate the average miss penalty for L1 cache for each of the cores
separately. I tried manipulating something in tbeTable.hh file but got stuck
because there is no way to identify the core to which that tbe
My last issue has been resolved with that patch (https://gem5-review.googlesource.com/c/public/gem5/+/49203). Thank you! ___
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%
Hi, All users
when I using latest gem5 v21.1.0.0 to run a simple se mode simulation like this:
./build/ARM/gem5.fast ./configs/example/se.py --cpu-type=AtomicSimpleCPU -c
./400.perlbench -o '-I./lib checkspam.pl 2500 5 25 11 150 1 1 1 1'
gem5 will report error like this:
se.py: error: argument -o/
