On Fri, Oct 2, 2015 at 11:37 PM, Connor Abbott <cwabbo...@gmail.com> wrote: > Now that we have three separate things we want to measure (instructions, > cycles, and loops), it's impractical to keep adding special code for > changes in each thing. Instead, for each program in before and after we > store a table of measurement -> value, and when reporting we loop over > each measurement and report helped/hurt before reporting the gained/lost > programs. > > Signed-off-by: Connor Abbott <cwabbo...@gmail.com> > --- > report.py | 140 > ++++++++++++++++++++++++++++++-------------------------------- > 1 file changed, 67 insertions(+), 73 deletions(-) > > diff --git a/report.py b/report.py > index 4c06714..bc3a640 100755 > --- a/report.py > +++ b/report.py > @@ -10,17 +10,22 @@ def get_results(filename): > > results = {} > > - re_match = re.compile(r"(\S+) - (.S \S+) shader: (\S*) inst, (\S*) > loops") > + re_match = re.compile(r"(\S+) - (.S \S+) shader: (\S*) inst, (\S*) > cycles, (\S*) loops") > for line in lines: > match = re.search(re_match, line) > if match is None: > continue > > groups = match.groups() > - count = int(groups[2]) > - loop = int(groups[3]) > - if count != 0: > - results[(groups[0], groups[1])] = count, loop > + inst_count = int(groups[2]) > + cycle_count = int(groups[3])
Something's up with the indentation here... _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev