I tried using compression, but I'm getting a segmentation fault error. This
happens regardless to whether I use an AtomicSimpleCPU and atomic mem mode
or TimingSimpleCPU and timing mem mode. The error is the same and occurs
after a WritebackDirty miss to the LLC.
I use the following command to run gem5 in debug mode:
run --debug-flags=Cache,CacheTags,CacheComp configs/example/se.py -c
/home/vic/Documents/tests/simple_array --cpu-type TimingSimpleCPU -n 1
--caches --l1d_size 128B --l1i_size 128B --l2cache --num-l2caches 1
--l2_size 512B --compression --compressor BDI
The error is the following:
Program received signal SIGSEGV, Segmentation fault.
0x0000000001030f92 in __gnu_cxx::__atomic_add (__mem=0x9, __val=1)
at /usr/include/c++/5/ext/atomicity.h:53
53 { __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); }
If I merge the changes from "Remove writebacks packet list" and don't use
Atomic mode, would that fix the problem?
Thanks
On Wed, 24 Jul 2019 at 16:23, Victor Kariofillis <vickariofil...@gmail.com>
wrote:
> Hi,
>
> I am interested in using the cache compression schemes that gem5 has
> (mainly BDI). I was going through the commits and I saw one named "Remove
> writebacks packet list", that was later reverted because it introduced a
> bug in atomic mode. Using a compression scheme will probably result in
> multiple evictions in the case of a writeback. Does this mean that I
> shouldn't use atomic mode along with compressed_tags (i.e. compression) as
> the reverted commit suggests? Is it fine if compression is used in timing
> mode?
>
> Thank you,
> Victor
>
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
