summaryrefslogtreecommitdiff
path: root/src/mem/protocol/MESI_Three_Level-L1cache.sm
diff options
context:
space:
mode:
authorNilay Vaish <nilay@cs.wisc.edu>2015-09-18 13:27:47 -0500
committerNilay Vaish <nilay@cs.wisc.edu>2015-09-18 13:27:47 -0500
commit216529bf182f58830cfccad090f348e1b8730675 (patch)
tree33a2c3f5d76118591e9dd6b7ac377a51de670d07 /src/mem/protocol/MESI_Three_Level-L1cache.sm
parentb3eb0d1423f26e42985ed23b84f71c858a8dd24e (diff)
downloadgem5-216529bf182f58830cfccad090f348e1b8730675.tar.xz
ruby: slicc: derive DataMember class from Var instead of PairContainer
The DataMember class in Type.py was being derived from PairContainer. A separate Var object was also created for the DataMember. This meant some duplication of across the members of these two classes (Var and DataMember). This patch changes DataMember from Var instead. There is no obvious reason to derive from PairContainer which can only hold pairs, something that Var class already supports. The only thing that DataMember has over Var is init_code, which is being retained. This change would later on help in having pointers in DataMembers.
Diffstat (limited to 'src/mem/protocol/MESI_Three_Level-L1cache.sm')
0 files changed, 0 insertions, 0 deletions