On Fri, Oct 2, 2015 at 2: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")
I'd like to keep results files generated before your series working,
so to do that we'll have to move cycles after loops.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
