Home
last modified time | relevance | path

Searched refs:VAOs (Results 1 – 21 of 21) sorted by relevance

/third_party/mesa3d/src/mesa/main/
Dglthread.c103 glthread->VAOs = _mesa_NewHashTable(); in _mesa_glthread_init()
104 if (!glthread->VAOs) { in _mesa_glthread_init()
114 _mesa_DeleteHashTable(glthread->VAOs); in _mesa_glthread_init()
173 _mesa_HashDeleteAll(glthread->VAOs, free_vao, NULL); in _mesa_glthread_destroy()
174 _mesa_DeleteHashTable(glthread->VAOs); in _mesa_glthread_destroy()
Dglthread_varray.c83 vao = _mesa_HashLookupLocked(glthread->VAOs, id); in lookup_vao()
137 _mesa_HashRemoveLocked(glthread->VAOs, vao->Name); in _mesa_glthread_DeleteVertexArrays()
162 _mesa_HashInsertLocked(glthread->VAOs, id, vao, true); in _mesa_glthread_GenVertexArrays()
Dglthread.h197 struct _mesa_HashTable *VAOs; member
/third_party/skia/third_party/externals/opengl-registry/extensions/ARB/
DARB_vertex_array_object.txt232 This allows applications using ARB VAOs to safely call into libraries that
233 internally use Apple VAOs, and vice-versa.
348 However, much of the state that is encapsulated by VAOs is client-state.
350 RESOLUTION: Resolved. VAOs are server state. This essentially means that
362 (3) Are VAOs sharable?
429 4 05/15/2008 idr Resolved issue #1. VAOs are server state.
430 Resolved issue #5. ARB and APPLE VAOs share
444 longer possible to define a VAOs with client
DARB_direct_state_access.txt3439 the remainder of section 10.3 to refer back to VAOs.
3913 The purpose of BindVertexBuffers for the VAOs it to quickly switch
DARB_vertex_buffer_object.txt154 - VAOs renamed to "buffer objects", to signify that they can be
/third_party/openGLES/extensions/ARB/
DARB_vertex_array_object.txt242 This allows applications using ARB VAOs to safely call into libraries that
243 internally use Apple VAOs, and vice-versa.
358 However, much of the state that is encapsulated by VAOs is client-state.
360 RESOLUTION: Resolved. VAOs are server state. This essentially means that
372 (3) Are VAOs sharable?
439 4 05/15/2008 idr Resolved issue #1. VAOs are server state.
440 Resolved issue #5. ARB and APPLE VAOs share
454 longer possible to define a VAOs with client
DARB_direct_state_access.txt3470 the remainder of section 10.3 to refer back to VAOs.
3944 The purpose of BindVertexBuffers for the VAOs it to quickly switch
DARB_vertex_buffer_object.txt164 - VAOs renamed to "buffer objects", to signify that they can be
/third_party/skia/third_party/externals/opengl-registry/extensions/OES/
DOES_vertex_array_object.txt81 the possibility of hurting adoption of VAOs.
427 be included in VAOs. Disallow sharing of VAOs.
/third_party/openGLES/extensions/OES/
DOES_vertex_array_object.txt91 the possibility of hurting adoption of VAOs.
437 be included in VAOs. Disallow sharing of VAOs.
/third_party/skia/third_party/externals/opengl-registry/extensions/AMD/
DAMD_name_gen_delete.txt142 - VERTEX_ARRAY_OBJECT_AMD (For VAOs instead of VERTEX_ARRAY_BINDING)
658 - VERTEX_ARRAY_OBJECT_AMD (For VAOs instead of VERTEX_ARRAY_BINDING)
678 VERTEX_ARRAY or VERTEX_ARRAY_BINDING and VAOs.
/third_party/openGLES/extensions/AMD/
DAMD_name_gen_delete.txt142 - VERTEX_ARRAY_OBJECT_AMD (For VAOs instead of VERTEX_ARRAY_BINDING)
658 - VERTEX_ARRAY_OBJECT_AMD (For VAOs instead of VERTEX_ARRAY_BINDING)
678 VERTEX_ARRAY or VERTEX_ARRAY_BINDING and VAOs.
/third_party/flutter/skia/third_party/externals/angle2/doc/
DDirtyBits.md45 state. [VAOs][VAOState] store vertex arrays and array buffer bindings. [Framebuffers][FBOState]
/third_party/skia/third_party/externals/angle2/doc/
DDirtyBits.md45 state. [VAOs][VAOState] store vertex arrays and array buffer bindings. [Framebuffers][FBOState]
/third_party/openGLES/extensions/NV/
DNV_instanced_arrays.txt364 3 20 Aug 2012 groth Add interaction with VAOs
DNV_vertex_buffer_unified_memory.txt344 are per-VAO and middleware libraries can/should use their own VAOs if
/third_party/skia/third_party/externals/opengl-registry/extensions/NV/
DNV_instanced_arrays.txt364 3 20 Aug 2012 groth Add interaction with VAOs
DNV_vertex_buffer_unified_memory.txt344 are per-VAO and middleware libraries can/should use their own VAOs if
/third_party/mesa3d/docs/relnotes/
D20.1.0.rst3065 - glthread: track VAOs created by CreateVertexArrays
3128 - mesa: optimize initialization of new VAOs
3228 - i965: Use the VAOs binding information in array setup.
D20.2.0.rst3180 - mesa,st/mesa: add a fast path for non-static VAOs
3189 - glthread: initialize VAOs properly