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

            Bug ID: 90669
           Summary: make check DispatchSanity_test.GLES3 regression
           Product: Mesa
           Version: 10.6
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Keywords: bisected, regression
          Severity: normal
          Priority: medium
         Component: Mesa core
          Assignee: mesa-dev@lists.freedesktop.org
          Reporter: v...@freedesktop.org
        QA Contact: mesa-dev@lists.freedesktop.org
                CC: bri...@vmware.com, i...@freedesktop.org

mesa: 8d813d14e1f5c690c6737c6cd6fc01937a7d4246 (master 10.7.0-devel)


$ make check
[...]
[ RUN      ] DispatchSanity_test.GL31_CORE
dispatch_sanity.cpp:170: Failure
Value of: table[i]
  Actual: 0x410350
Expected: nop_table[i]
Which is: 0x7f339f061750
i = 0 (NewList)
dispatch_sanity.cpp:170: Failure
[...]
Value of: table[i]
  Actual: 0x410350
Expected: nop_table[i]
Which is: 0x7f339f05c230
i = 1559 (???)
[  FAILED  ] DispatchSanity_test.GLES3 (27 ms)


commit be71bbfaa2ad201b570b56847a13328fc359d0ee
Author: Brian Paul <bri...@vmware.com>
Date:   Fri May 15 09:08:14 2015 -0600

    mesa: do not use _glapi_new_nop_table() for DRI builds

    Commit 4bdbb588a9d38 introduced new _glapi_new_nop_table() and
    _glapi_set_nop_handler() functions in the glapi dispatcher (which
    live in libGL.so).  The calls to those functions from context.c
    would be undefined (i.e. an ABI break) if the libGL used at runtime
    was older.

    For the time being, use the old single generic_nop() function for
    non-Windows builds to avoid this problem.  At some point in the future
    it should be safe to remove this work-around.  See comments for more
    details.

    v2: Incorporate feedback from Emil.  Use _WIN32 instead of
    GLX_DIRECT_RENDERING to control behavior, move comments.

    Cc: 10.6 <mesa-sta...@lists.freedesktop.org>
    Reviewed-and-tested-by: Ian Romanick <ian.d.roman...@intel.com>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to