On Thu, 2015-12-10 at 09:47 -0800, Matt Turner wrote:
> Assuming that the cause is indeed non-orthogonal state changes, yes.
> But I never saw an answer to that question.
>
> Reviewed-by: Matt Turner
After rebasing and testing against master (11.1-branchpoint-653-
g5c5ad4d)
On Mon, 2015-11-30 at 12:26 +0100, Juan A. Suarez Romero wrote:
> When using INTEL_DEBUG=optimizer, each optimizing step is dump to
> disk,
> in a separate file.
Any news on this? Can be considered as reviewed? Thanks in advance
J.A.
___
On Thu, Dec 10, 2015 at 8:44 AM, Juan A. Suarez Romero
wrote:
> On Mon, 2015-11-30 at 12:26 +0100, Juan A. Suarez Romero wrote:
>> When using INTEL_DEBUG=optimizer, each optimizing step is dump to
>> disk,
>> in a separate file.
>
>
> Any news on this? Can be considered as
When using INTEL_DEBUG=optimizer, each optimizing step is dump to disk,
in a separate file.
But as fs_visitor::optimize() and vec4_visitor::run() are called more
than once, it ends up overwriting the files already on disk, loosing
then previous optimizer steps.
To avoid this, add a new static