On Thu, Nov 11, 2010 at 7:29 PM, nathan binkert wrote:
> > This is the convention I've been using:
> > (1) To maintain instance variable naming conventions, I have named the
> > stats variables using lowerCamelCase.
> > (2) For stat string output printed to stats.txt, I've used
> > lower_unde
> This is the convention I've been using:
> (1) To maintain instance variable naming conventions, I have named the
> stats variables using lowerCamelCase.
> (2) For stat string output printed to stats.txt, I've used
> lower_underscore.
> It looks like the majority of stats.txt output strings ar
This is the convention I've been using:
(1) To maintain instance variable naming conventions, I have named the
stats variables using lowerCamelCase.
(2) For stat string output printed to stats.txt, I've used
lower_underscore.
It looks like the majority of stats.txt output strings are in
lower_
> I think the current situation is basically historical... the stats names
> with underscores were inherited from SimpleScalar, and then we we went with
> camelCase for variable names there was an inherent mismatch that has at
> times been perpetuated and at other times ignored.
True.
> It would b
On Thu, Nov 4, 2010 at 12:21 PM, nathan binkert wrote:
> > I'm currently trying to leverage a Python script and McPAT to consume
> M5
> > statistics (stats.txt) and calculate power estimates for a simulated
> system.
> > Stats variables in the SimObjects are lowerCamelCase according to the
> >
> I'm currently trying to leverage a Python script and McPAT to consume M5
> statistics (stats.txt) and calculate power estimates for a simulated system.
> Stats variables in the SimObjects are lowerCamelCase according to the
> coding style, but it looks like the names output to the stats.txt fi
