[Bug 108624] [regression][bisected] "nir: Copy propagation between blocks" regression

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Nov 1 11:32:00 UTC 2018


            Bug ID: 108624
           Summary: [regression][bisected] "nir: Copy propagation between
                    blocks" regression
           Product: Mesa
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: apinheiro at igalia.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Created attachment 142326
  --> https://bugs.freedesktop.org/attachment.cgi?id=142326&action=edit
regression test

Not sure if it is normal to create [regression] bugs for tests that are not on
any upstream branch, but as today is a bank day here in Spain, I will not have
time for triagging for some days, so I prefer to save it somewhere, in order to
not forget about it.

Initially I found it while testing ARB_gl_spirv with borrowed tests (tests from
other specs). But it also fails with vulkan, by using vkrunner.

So, attached the ARB_gl_spirv test. Can also be found here:

And the vkrunner equivalent here:

FWIW, the ARB_gl_spirv test is executed as any other piglit shader_test,
although it needs to override the extension, so:
tests/spec/arb_gl_spirv/execution/fs-large-local-array-vec4.shader_test -auto

After bisecting, the candidates for the guilty commits are:

* dc349f07b5f9c257f68ecf0cbb89f9722a42233a ("nir: Take call instruction into
account in copy_prop_vars")
* b3c6146925595ec3a7eece3afb9ccaad32906d4c ("nir: Copy propagation between

I have two candidates because the first commit doesn't build correctly ("error:
‘copies’ undeclared (first use in this function)")

Those commits changes nir_opt_copy_prop_vars among other things. And in fact,
if we don't call that optimization (dirty hack just to scope where the problem
is), the test goes back to passing (although everything gets slower).

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20181101/764ce6b1/attachment.html>

More information about the intel-3d-bugs mailing list