[Bug 109353] [regression][bisected] "nir: Switch to using 1-bit Booleans for almost everything" regression with shared bools

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 14 14:28:58 UTC 2019


            Bug ID: 109353
           Summary: [regression][bisected] "nir: Switch to using 1-bit
                    Booleans for almost everything" regression with shared
           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

Since the following commit:

"commit 44227453ec03f5462f1cff5760909a9dba95c61a
Author: Jason Ekstrand <jason.ekstrand at intel.com>
Date:   Fri Oct 19 11:14:47 2018 -0500

    nir: Switch to using 1-bit Booleans for almost everything

    This is a squash of a few distinct changes:

        glsl,spirv: Generate 1-bit Booleans

        Revert "Use 32-bit opcodes in the NIR producers and optimizations"

        Revert "nir/builder: Generate 32-bit bool opcodes transparently"

        nir/builder: Generate 1-bit Booleans in nir_build_imm_bool

    Reviewed-by: Eric Anholt <eric at anholt.net>
    Reviewed-by: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>
    Tested-by: Bas Nieuwenhuizen <bas at basnieuwenhuizen.nl>"

Using a shared bool on a compute shader raises the following assert:
  SPIR-V parsing FAILED:
    In file ../src/compiler/spirv/vtn_variables.c:406
    base->ptr_type->length > 0 && base->ptr_type->align > 0
    1028 bytes into the SPIR-V binary
shader_runner: ../src/mesa/main/glspirv.c:268: _mesa_spirv_to_nir: Assertion
`entry_point' failed.
Aborted (core dumped)

Although I initially found this while testing ARB_gl_spirv, I confirmed that it
also happens on anv Vulkan. I will submit a vkrunner test soon.

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

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