Re: [Gems-users] getCacheEntry()

["hongxia sun" <sunhx.seraph@xxxxxxxxx>]

Hi Dave,

 

"CacheMemory<ENTRY>::lookup(const Address&) " is called in many functions in CacheMemory class. The failed assertion might cause by your protocol. Because each transition will according to your cache state, and then it will do corresponding actions. If the actions violate the cache entry's state, such failure will occur.

 

Trace which transition and which action caused the failure and then you can fix the problem.

 

Good luck!

 

Hongxia SUN

 

2007/3/17, Dave Z. <zhu_dave@xxxxxxxxx>:

Hello,

I have a question regarding getCacheEntry(). In my
SLICC file, I do the following:

...
if (isCacheTagPresent(myAddr)) {
if (getState(myAddr) == State:I) {
   trigger(Event:myEvent, myAddr);
}
}
...

The event makes a call to getCacheEntry(), which
raises the following issue:

failed assertion 'loc != -1' at fn ENTRY&
CacheMemory<ENTRY>::lookup(const Address&) [with ENTRY
= L1Cache_Entry] in system/CacheMemory.h:497

I don't understand why the entry is not found in the
cache, because isCacheTagPresent() already found it in
the cache.

Thanks,

Dave



____________________________________________________________________________________
Sucker-punch spam with award-winning protection.
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.