Searched hist:8341 (Results 1 - 3 of 3) sorted by relevance
/gem5/src/mem/slicc/ast/ | ||
H A D | MethodCallExprAST.py | 8341:30daf1dd5c91 Wed Jun 08 12:58:00 EDT 2011 Nilay Vaish<nilay@cs.wisc.edu> Ruby: Correctly set access permissions for directory entries The access permissions for the directory entries are not being set correctly. This is because pointers are not used for handling directory entries. function. get and set functions for access permissions have been added to the Controller state machine. The changePermission() function provided by the AbstractEntry and AbstractCacheEntry classes has been exposed to SLICC code once again. The set_permission() functionality has been removed. NOTE: Each protocol will have to define these get and set functions in order to compile successfully. |
/gem5/src/mem/ruby/slicc_interface/ | ||
H A D | AbstractController.hh | 8341:30daf1dd5c91 Wed Jun 08 12:58:00 EDT 2011 Nilay Vaish<nilay@cs.wisc.edu> Ruby: Correctly set access permissions for directory entries The access permissions for the directory entries are not being set correctly. This is because pointers are not used for handling directory entries. function. get and set functions for access permissions have been added to the Controller state machine. The changePermission() function provided by the AbstractEntry and AbstractCacheEntry classes has been exposed to SLICC code once again. The set_permission() functionality has been removed. NOTE: Each protocol will have to define these get and set functions in order to compile successfully. |
/gem5/src/mem/slicc/symbols/ | ||
H A D | StateMachine.py | 8341:30daf1dd5c91 Wed Jun 08 12:58:00 EDT 2011 Nilay Vaish<nilay@cs.wisc.edu> Ruby: Correctly set access permissions for directory entries The access permissions for the directory entries are not being set correctly. This is because pointers are not used for handling directory entries. function. get and set functions for access permissions have been added to the Controller state machine. The changePermission() function provided by the AbstractEntry and AbstractCacheEntry classes has been exposed to SLICC code once again. The set_permission() functionality has been removed. NOTE: Each protocol will have to define these get and set functions in order to compile successfully. |
Completed in 55 milliseconds