[Bug 109532] ir_variable has maximum access out of bounds -- but it's not out of bounds

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Feb 2 09:10:37 UTC 2019


            Bug ID: 109532
           Summary: ir_variable has maximum access out of bounds -- but
                    it's not out of bounds
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: glsl-compiler
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: imirkin at alum.mit.edu
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Created attachment 143274
  --> https://bugs.freedesktop.org/attachment.cgi?id=143274&action=edit
gdb session + generated shaders

This dEQP test asserts, at least on nouveau, but I don't see what would cause
it to be driver-specific.


This appears to happen because it doesn't understand the interface array index
properly? This message is printed before the abort:

ir_variable has maximum access out of bounds (1 vs 0)

For some reason it thinks that the array length is 1 when it should be 2. I
recall interfaces being treated rather differently than most things, so perhaps

You are receiving this mail because:
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/20190202/92c4906b/attachment.html>

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