[mailto:m5-dev-boun...@m5sim.org]
On Behalf Of Nilay Vaish
Sent: Tuesday, January 18, 2011 10:45 AM
To: M5 Developer List
Subject: Re: [m5-dev] Question on SLICC
Figured that out last night. I also noticed that there is comment about
it in
RubySlicc_Types.sm (should read files more
There are certain types defined in the file
src/mem/protocol/RubySlicc_Types.sm. For each of the type is .hh is gets
written which contains the path of the actual header file to be used. For
example, the file RubySlicc_Types.sm defines CacheMemory type. This type is
actually defined in the
of the libruby files.
Brad
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org]
On Behalf Of Nilay Vaish
Sent: Tuesday, January 18, 2011 10:45 AM
To: M5 Developer List
Subject: Re: [m5-dev] Question on SLICC
Figured that out last night. I also noticed
? If not, I would like to get rid of the libruby
files.
Brad
-Original Message-
From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org]
On Behalf Of Nilay Vaish
Sent: Tuesday, January 18, 2011 10:45 AM
To: M5 Developer List
Subject: Re: [m5-dev] Question on SLICC
Figured
There are certain types defined in the file
src/mem/protocol/RubySlicc_Types.sm. For each of the type is .hh is gets
written which contains the path of the actual header file to be used. For
example, the file RubySlicc_Types.sm defines CacheMemory type. This type
is actually defined in the