Re: [Mesa-dev] [PATCH shader-db 1/2] report.py: rework and update for cycle info

On Fri, Oct 2, 2015 at 2:37 PM, Connor Abbott 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 >

Re: [Mesa-dev] [PATCH shader-db 1/2] report.py: rework and update for cycle info

On Fri, Oct 2, 2015 at 11:37 PM, Connor Abbott 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 >

[Mesa-dev] [PATCH shader-db 1/2] report.py: rework and update for cycle info

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