The BRW functions that run then optimizations in the FS (fs_visitor::optimize()) and in the VS (vec4_visitor::run()) can be called more than once.
This means when using INTEL_DEBUG=optimizer the output files with the optimization in each step are overwritten in successive calls. The quick and easiest fix is adding a new variable that is part of the filename (as iteration and pass_num), but that never is re-initialized to 0, and that indicates the call number. So this way we don't loose any in-between file. Adding a new variable instead of not initializing to 0 one of the others (like iteration) make it easier to indentify for each file in which call it was generated. As example, in original master I get 138 files for FS/VS optimizations when running a piglit test, while now I get 225, meaning I'm recovering 87 missing steps. Juan A. Suarez Romero (1): i965: Do not overwrite optimizer dumps src/mesa/drivers/dri/i965/brw_fs.cpp | 13 +++++++++---- src/mesa/drivers/dri/i965/brw_vec4.cpp | 11 +++++++---- 2 files changed, 16 insertions(+), 8 deletions(-) -- 2.5.0 _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
