1Name 2 3 ANGLE_explicit_context 4 5Name Strings 6 7 EGL_ANGLE_explicit_context 8 9Contributors 10 11 Brandon Jones, Intel 12 13Contacts 14 15 Brandon Jones, Intel (brandon1.jones 'at' intel 'dot' com) 16 17Status 18 19 Complete. 20 21Version 22 23 Version 1, 2018-5-22 24 25Number 26 27 EGL Extension XXX 28 29Extension Type 30 31 EGL Client Extension 32 33Dependencies 34 35 OpenGL ES 3.1 is required. 36 37 EGL_KHR_get_all_proc_addresses is required. 38 39 EGL_EXT_client_extensions is required. 40 41Overview 42 43 This extension adds new OpenGL ES entry points that allow the user to pass the current EGL 44 context as a function parameter. This allows users to skip lookup of the thread's current 45 context upon entry. 46 47New Types 48 49 None. 50 51New Procedures and Functions 52 53 For every OpenGL ES entry point available through eglGetProcAddress, an additional entry point 54 is made available. The entry points have the form of: 55 56 <return value> gl<entry point name>ContextANGLE(GLeglContextANGLE context, <entry point parameters>) 57 58 If a function already has an extension suffix, this form still applies. 59 60New Tokens 61 62 None. 63 64Additions to the EGL Specification 65 66 When using OpenGL ES as a client library, the ContextANGLE entry points allow the user to 67 pass the current EGL context as a function parameter to provide better performance than 68 looking up the current EGL context at every GL entry point. 69 70 Calls made with an explicit context provide no additional validation for the passed context 71 parameter. 72 73 Calls made with an explicit context will generate errors under the same conditions as they 74 would without an explicit context. Any instances of undefined behaviour without specifying 75 an explicit context are still undefined when specifying an explicit context. 76 77 When an EGL context that is not current is explicitly passed, the resulting behavior is 78 undefined. 79 80Issues 81 82 None. 83 84Revision History 85 86 Version 1, 2018-5-22 (Brandon Jones) 87 - Initial draft