[Bug 110432] dEQP-VK tests running very long time

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=110432

            Bug ID: 110432
           Summary: dEQP-VK tests running very long time
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: lemody at gmail.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Some of the dEQP-VK tests spend a lot of time in compiler. In particular these
2 ones are heavily affected:

dEQP-VK.spirv_assembly.instruction.graphics.8bit_storage.32struct_to_8struct.storage_buffer_sint_geom
dEQP-VK.spirv_assembly.instruction.graphics.8bit_storage.32struct_to_8struct.storage_buffer_uint_geom

Normally with old Mesa take take 2-3 secs to complete but with current git I
measured today 38 minutes 43 seconds (!)


I've bisected this to following commit:

-------------- 8< -----------------------------
commit b031c643491a92a5574c7a4bd659df33f2d89bb6
Author: Ian Romanick <ian.d.romanick at intel.com>
Date:   Thu Jan 17 17:53:40 2019 -0800

    nir: Convert a bcsel with only phi node sources to a phi node

    v2: Remove the original ALU instruciton after all of its readers are
    modified to read the new ALU instruction.

    v3: Fix an issue where a bcsel that may not be executed on a loop
    iteration due to a break statement is converted to a phi (and therefore
    incorrectly "executed").  Noticed by Tim.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109216
    Fixes: 8fb8ebfbb05 ("intel/compiler: More peephole select")
    Reviewed-by: Timothy Arceri <tarceri at itsqueeze.com>

-- 
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/20190415/bee2ea9a/attachment.html>