I would also like to know the answer to this question, if anyone is able to answer it.
Thanks, Marc On Thu, Jun 23, 2011 at 5:02 PM, Jason Power <[email protected]> wrote: > Hi all, > > When I try to create an L1 cache in Ruby that is fully associative I get > the following error: > > gem5.debug: build/X86_SE_G3_VI_L2/mem/ruby/system/CacheMemory.cc:65: >> virtual void CacheMemory::init(): Assertion `m_cache_num_sets > 1' >> failed. Program aborted at cycle 0 >> Aborted > > > After investigating the code, it seems that this assert is used to force > the cache to always have at least 2 sets, simplifying the bit select logic. > Is there any inherent reason Ruby doesn't support a fully associative cache? > It seems like a straightforward fix, I just wanted to make sure I wasn't > missing something. > > Thanks, > Jason > > > ------ > Jason Power > University of Wisconsin-Madison, > Department of Computer Sciences > [email protected] > > > > _______________________________________________ > 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
