DOCSLIB.ORG

Opengl 4.6 (Core Profile)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Opengl 4.6 (Core Profile) The OpenGL R Graphics System: A Specification (Version 4.6 (Core Profile) - October 22, 2019) Mark Segal Kurt Akeley Editor (version 1.1): Chris Frazier Editor (versions 1.2-4.6 ): Jon Leech Editor (version 2.0): Pat Brown Copyright c 2006-2019 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to Khronos. Except as described by these terms, it or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of Khronos. This specification has been created under the Khronos Intellectual Property Rights Policy, which is Attachment A of the Khronos Group Membership Agreement available at www.khronos.org/files/member agreement.pdf. Khronos grants a con- ditional copyright license to use and reproduce the unmodified specification for any purpose, without fee or royalty, EXCEPT no licenses to any patent, trade- mark or other intellectual property rights are granted under these terms. Parties desiring to implement the specification and make use of Khronos trademarks in relation to that implementation, and receive reciprocal patent license protection under the Khronos IP Policy must become Adopters and confirm the implementa- tion as conformant under the process defined by Khronos for this specification; see https://www.khronos.org/adopters. Khronos makes no, and expressly disclaims any, representations or warranties, ex- press or implied, regarding this specification, including, without limitation: mer- chantability, fitness for a particular purpose, non-infringement of any intellectual property, correctness, accuracy, completeness, timeliness, and reliability. Under no circumstances will Khronos, or any of its Promoters, Contributors or Members, or their respective partners, officers, directors, employees, agents or representatives be liable for any damages, whether direct, indirect, special or consequential damages for lost revenues, lost profits, or otherwise, arising from or in connection with these materials. Vulkan and Khronos are registered trademarks, and WebGL and EGL are trade- marks of The Khronos Group Inc. ASTC is a trademark of ARM Holdings PLC; OpenCL is a trademark of Apple Inc.; and OpenGL is a registered trademark, and the OpenGL ES and OpenGL SC logos are trademarks of Hewlett Packard Enter- prise, all used under license by Khronos. All other product names, trademarks, and/or company names are used solely for identification and belong to their respec- tive owners. Contents 1 Introduction1 1.1 Formatting of the OpenGL Specification . .1 1.1.1 Formatting of the Compatibility Profile . .1 1.1.2 Formatting of Optional Features . .1 1.1.3 Formatting of Changes . .2 1.2 What is the OpenGL Graphics System? . .2 1.2.1 Programmer’s View of OpenGL . .2 1.2.2 Implementor’s View of OpenGL . .3 1.2.3 Our View . .3 1.2.4 Fixed-function Hardware and the Compatibility Profile . .3 1.2.5 The Deprecation Model . .4 1.3 Related APIs . .4 1.3.1 OpenGL Shading Language . .4 1.3.2 OpenGL ES . .5 1.3.3 OpenGL ES Shading Language . .5 1.3.4 SPIR-V . .6 1.3.5 WebGL . .6 1.3.6 Window System Bindings . .6 1.3.7 OpenCL . .7 1.4 Filing Bug Reports . .7 2 OpenGL Fundamentals9 2.1 Execution Model . .9 2.2 Command Syntax . 11 2.2.1 Data Conversion For State-Setting Commands . 13 2.2.2 Data Conversions For State Query Commands . 15 2.3 Command Execution . 16 2.3.1 Errors . 17 2.3.2 Graphics Reset Recovery . 20 i CONTENTS ii 2.3.3 Flush and Finish . 21 2.3.4 Numeric Representation and Computation . 22 2.3.5 Fixed-Point Data Conversions . 25 2.4 Rendering Commands . 27 2.5 Context State . 28 2.5.1 Generic Context State Queries . 28 2.6 Objects and the Object Model . 28 2.6.1 Object Management . 29 2.6.2 Buffer Objects . 30 2.6.3 Shader Objects . 30 2.6.4 Program Objects . 30 2.6.5 Program Pipeline Objects . 31 2.6.6 Texture Objects . 31 2.6.7 Sampler Objects . 31 2.6.8 Renderbuffer Objects . 32 2.6.9 Framebuffer Objects . 32 2.6.10 Vertex Array Objects . 32 2.6.11 Transform Feedback Objects . 32 2.6.12 Query Objects . 33 2.6.13 Sync Objects . 33 2.6.14 Display Lists . 33 3 Dataflow Model 34 4 Event Model 37 4.1 Sync Objects and Fences . 37 4.1.1 Waiting for Sync Objects . 39 4.1.2 Signaling . 41 4.1.3 Sync Object Queries . 42 4.2 Query Objects and Asynchronous Queries . 43 4.2.1 Query Object Types and Targets . 43 4.2.2 Query Object Creation and Activation . 44 4.2.3 Query Object Queries . 48 4.3 Time Queries . 52 5 Shared Objects and Multiple Contexts 54 5.1 Object Deletion Behavior . 55 5.1.1 Side Effects of Shared Context Destruction . 55 5.1.2 Automatic Unbinding of Deleted Objects . 55 5.1.3 Deleted Object and Object Name Lifetimes . 55 OpenGL 4.6 (Core Profile) - October 22, 2019 CONTENTS iii 5.2 Sync Objects and Multiple Contexts . 56 5.3 Propagating Changes to Objects . 56 5.3.1 Determining Completion of Changes to an object . 57 5.3.2 Definitions . 58 5.3.3 Rules . 58 6 Buffer Objects 60 6.1 Creating and Binding Buffer Objects . 61 6.1.1 Binding Buffer Objects to Indexed Targets . 63 6.2 Creating and Modifying Buffer Object Data Stores . 66 6.2.1 Clearing Buffer Object Data Stores . 72 6.3 Mapping and Unmapping Buffer Data . 74 6.3.1 Unmapping Buffers . 79 6.3.2 Effects of Mapping Buffers on Other GL Commands . 80 6.4 Effects of Accessing Outside Buffer Bounds . 80 6.5 Invalidating Buffer Data . 81 6.6 Copying Between Buffers . 81 6.7 Buffer Object Queries . 82 6.7.1 Indexed Buffer Object Limits and Binding Queries . 84 6.8 Buffer Object State . 85 7 Programs and Shaders 88 7.1 Shader Objects . 89 7.2 Shader Binaries . 92 7.2.1 Shader Specialization . 94 7.3 Program Objects . 95 7.3.1 Program Interfaces . 103 7.4 Program Pipeline Objects . 122 7.4.1 Shader Interface Matching . 126 7.4.2 SPIR-V Shader Interface Matching . 129 7.4.3 Program Pipeline Object State . 130 7.5 Program Binaries . 131 7.6 Uniform Variables . 133 7.6.1 Loading Uniform Variables In The Default Uniform Block 142 7.6.2 Uniform Blocks . 145 7.6.3 Uniform Buffer Object Bindings . 150 7.7 Atomic Counter Buffers . 151 7.7.1 Atomic Counter Buffer Object Storage . 151 7.7.2 Atomic Counter Buffer Bindings . 151 7.8 Shader Buffer Variables and Shader Storage Blocks . 152 OpenGL 4.6 (Core Profile) - October 22, 2019 CONTENTS iv 7.9 Invocation Groups . 154 7.10 Subroutine Uniform Variables . 155 7.11 Samplers . 158 7.12 Images . 159 7.13 Shader Memory Access . 160 7.13.1 Shader Memory Access Ordering . 160 7.13.2 Shader Memory Access Synchronization . 162 7.14 Shader, Program, and Program Pipeline Queries . 167 7.15 Required State . 176 8 Textures and Samplers 179 8.1 Texture Objects . 180 8.2 Sampler Objects . 184 8.3 Sampler Object Queries . 189 8.4 Pixel Rectangles . 189 8.4.1 Pixel Storage Modes and Pixel Buffer Objects . 190 8.4.2 The Imaging Subset . 191 8.4.3 Pixel Transfer Modes . 191 8.4.4 Transfer of Pixel Rectangles . 191 8.4.5 Pixel Transfer Operations . 204 8.5 Texture Image Specification . 204 8.5.1 Required Texture Formats . 207 8.5.2 Encoding of Special Internal Formats . 208 8.5.3 Texture Image Structure . 212 8.6 Alternate Texture Image Specification Commands . 219 8.6.1 Texture Copying Feedback Loops . 226 8.7 Compressed Texture Images . 226 8.8 Multisample Textures . 234 8.9 Buffer Textures . 235 8.10 Texture Parameters . 239 8.11 Texture Queries . 243 8.11.1 Active Texture . 243 8.11.2 Texture Parameter Queries . 243 8.11.3 Texture Level Parameter Queries . 244 8.11.4 Texture Image Queries . 247 8.12 Depth Component Textures . 253 8.13 Cube Map Texture Selection . 254 8.13.1 Seamless Cube Map Filtering . 254 8.14 Texture Minification . ..
Load more

Recommended publications
  • Introduction to the Vulkan Computer Graphics API
    1 Introduction to the Vulkan Computer Graphics API Mike Bailey mjb – July 24, 2020 2 Computer Graphics Introduction to the Vulkan Computer Graphics API Mike Bailey [email protected] SIGGRAPH 2020 Abridged Version This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License http://cs.oregonstate.edu/~mjb/vulkan ABRIDGED.pptx mjb – July 24, 2020 3 Course Goals • Give a sense of how Vulkan is different from OpenGL • Show how to do basic drawing in Vulkan • Leave you with working, documented, understandable sample code http://cs.oregonstate.edu/~mjb/vulkan mjb – July 24, 2020 4 Mike Bailey • Professor of Computer Science, Oregon State University • Has been in computer graphics for over 30 years • Has had over 8,000 students in his university classes • [email protected] Welcome! I’m happy to be here. I hope you are too ! http://cs.oregonstate.edu/~mjb/vulkan mjb – July 24, 2020 5 Sections 13.Swap Chain 1. Introduction 14.Push Constants 2. Sample Code 15.Physical Devices 3. Drawing 16.Logical Devices 4. Shaders and SPIR-V 17.Dynamic State Variables 5. Data Buffers 18.Getting Information Back 6. GLFW 19.Compute Shaders 7. GLM 20.Specialization Constants 8. Instancing 21.Synchronization 9. Graphics Pipeline Data Structure 22.Pipeline Barriers 10.Descriptor Sets 23.Multisampling 11.Textures 24.Multipass 12.Queues and Command Buffers 25.Ray Tracing Section titles that have been greyed-out have not been included in the ABRIDGED noteset, i.e., the one that has been made to fit in SIGGRAPH’s reduced time slot.
    [Show full text]
  • GLSL 4.50 Spec
    The OpenGL® Shading Language Language Version: 4.50 Document Revision: 7 09-May-2017 Editor: John Kessenich, Google Version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost Copyright (c) 2008-2017 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
    [Show full text]
  • Opencl on the GPU San Jose, CA | September 30, 2009
    OpenCL on the GPU San Jose, CA | September 30, 2009 Neil Trevett and Cyril Zeller, NVIDIA Welcome to the OpenCL Tutorial! • Khronos and industry perspective on OpenCL – Neil Trevett Khronos Group President OpenCL Working Group Chair NVIDIA Vice President Mobile Content • NVIDIA and OpenCL – Cyril Zeller NVIDIA Manager of Compute Developer Technology Khronos and the OpenCL Standard Neil Trevett OpenCL Working Group Chair, Khronos President NVIDIA Vice President Mobile Content Copyright Khronos 2009 Who is the Khronos Group? • Consortium creating open API standards ‘by the industry, for the industry’ – Non-profit founded nine years ago – over 100 members - any company welcome • Enabling software to leverage silicon acceleration – Low-level graphics, media and compute acceleration APIs • Strong commercial focus – Enabling members and the wider industry to grow markets • Commitment to royalty-free standards – Industry makes money through enabled products – not from standards themselves Silicon Community Software Community Copyright Khronos 2009 Apple Over 100 companies creating authoring and acceleration standards Board of Promoters Processor Parallelism CPUs GPUs Multiple cores driving Emerging Increasingly general purpose performance increases Intersection data-parallel computing Improving numerical precision Multi-processor Graphics APIs programming – Heterogeneous and Shading e.g. OpenMP Computing Languages Copyright Khronos 2009 OpenCL Commercial Objectives • Grow the market for parallel computing • Create a foundation layer for a parallel
    [Show full text]
  • History and Evolution of the Android OS
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Springer - Publisher Connector CHAPTER 1 History and Evolution of the Android OS I’m going to destroy Android, because it’s a stolen product. I’m willing to go thermonuclear war on this. —Steve Jobs, Apple Inc. Android, Inc. started with a clear mission by its creators. According to Andy Rubin, one of Android’s founders, Android Inc. was to develop “smarter mobile devices that are more aware of its owner’s location and preferences.” Rubin further stated, “If people are smart, that information starts getting aggregated into consumer products.” The year was 2003 and the location was Palo Alto, California. This was the year Android was born. While Android, Inc. started operations secretly, today the entire world knows about Android. It is no secret that Android is an operating system (OS) for modern day smartphones, tablets, and soon-to-be laptops, but what exactly does that mean? What did Android used to look like? How has it gotten where it is today? All of these questions and more will be answered in this brief chapter. Origins Android first appeared on the technology radar in 2005 when Google, the multibillion- dollar technology company, purchased Android, Inc. At the time, not much was known about Android and what Google intended on doing with it. Information was sparse until 2007, when Google announced the world’s first truly open platform for mobile devices. The First Distribution of Android On November 5, 2007, a press release from the Open Handset Alliance set the stage for the future of the Android platform.
    [Show full text]
  • Rowpro Graphics Tester Instructions
    RowPro Graphics Tester Instructions What is the RowPro Graphics Tester? The RowPro Graphics Tester is a handy utility to quickly check and confirm RowPro 3D graphics and live water will run in your PC. Do I need to test my PC graphics? If any of the following are true you should test your PC graphics before installing or upgrading to RowPro 3: If your PC shipped new with Windows XP. If you are about to upgrade from RowPro version 2. If you have any doubts or concerns about your PC graphics system. How to download and install the RowPro Graphics Tester Click the link above to download the tester file RowProGraphicsTest.exe. In the download dialog box that appears, click Save or Save this program to disk, navigate to the folder where you want to save the download, and click OK to start the download. IMPORTANT NOTE: The RowPro Graphics Tester only tests if your PC has the required graphics components installed, it is not a graphics performance test. Passing the RowPro Graphics Test is not a guarantee that your PC will run RowPro at a frame rate that is fast enough to be useful. It is however an important test to confirm your PC is at least equipped with the necessary graphics components. How to run the RowPro Graphics Tester 1. Run RowProGraphicsTest.exe to run the test. The test normally completes in less than a second. 2. If any of the results show 'No', check the solutions below. 3. Click the x at the top right of the test panel to close the test.
    [Show full text]
  • Opengl Shading Languag 2Nd Edition (Orange Book)
    OpenGL® Shading Language, Second Edition By Randi J. Rost ............................................... Publisher: Addison Wesley Professional Pub Date: January 25, 2006 Print ISBN-10: 0-321-33489-2 Print ISBN-13: 978-0-321-33489-3 Pages: 800 Table of Contents | Index "As the 'Red Book' is known to be the gold standard for OpenGL, the 'Orange Book' is considered to be the gold standard for the OpenGL Shading Language. With Randi's extensive knowledge of OpenGL and GLSL, you can be assured you will be learning from a graphics industry veteran. Within the pages of the second edition you can find topics from beginning shader development to advanced topics such as the spherical harmonic lighting model and more." David Tommeraasen, CEO/Programmer, Plasma Software "This will be the definitive guide for OpenGL shaders; no other book goes into this detail. Rost has done an excellent job at setting the stage for shader development, what the purpose is, how to do it, and how it all fits together. The book includes great examples and details, and good additional coverage of 2.0 changes!" Jeffery Galinovsky, Director of Emerging Market Platform Development, Intel Corporation "The coverage in this new edition of the book is pitched just right to help many new shader- writers get started, but with enough deep information for the 'old hands.'" Marc Olano, Assistant Professor, University of Maryland "This is a really great book on GLSLwell written and organized, very accessible, and with good real-world examples and sample code. The topics flow naturally and easily, explanatory code fragments are inserted in very logical places to illustrate concepts, and all in all, this book makes an excellent tutorial as well as a reference." John Carey, Chief Technology Officer, C.O.R.E.
    [Show full text]
  • Migrating from Opengl to Vulkan Mark Kilgard, January 19, 2016 About the Speaker Who Is This Guy?
    Migrating from OpenGL to Vulkan Mark Kilgard, January 19, 2016 About the Speaker Who is this guy? Mark Kilgard Principal Graphics Software Engineer in Austin, Texas Long-time OpenGL driver developer at NVIDIA Author and implementer of many OpenGL extensions Collaborated on the development of Cg First commercial GPU shading language Recently working on GPU-accelerated vector graphics (Yes, and wrote GLUT in ages past) 2 Motivation for Talk Coming from OpenGL, Preparing for Vulkan What kinds of apps benefit from Vulkan? How to prepare your OpenGL code base to transition to Vulkan How various common OpenGL usage scenarios are re-thought in Vulkan Re-thinking your application structure for Vulkan 3 Analogy Different Valid Approaches 4 Analogy Fixed-function OpenGL Pre-assembled toy car fun out of the box, not much room for customization 5 AZDO = Approaching Zero Driver Overhead Analogy Modern AZDO OpenGL with Programmable Shaders LEGO Kit you build it yourself, comes with plenty of useful, pre-shaped pieces 6 Analogy Vulkan Pine Wood Derby Kit you build it yourself to race from raw materials power tools used to assemble, adult supervision highly recommended 7 Analogy Different Valid Approaches Fixed-function OpenGL Modern AZDO OpenGL with Vulkan Programmable Shaders 8 Beneficial Vulkan Scenarios Has Parallelizable CPU-bound Graphics Work yes Can your graphics Is your graphics work start work creation be CPU bound? parallelized? yes Vulkan friendly 9 Beneficial Vulkan Scenarios Maximizing a Graphics Platform Budget You’ll yes do whatever Your graphics start it takes to squeeze platform is fixed out max perf. yes Vulkan friendly 10 Beneficial Vulkan Scenarios Managing Predictable Performance, Free of Hitching You put yes You can a premium on manage your start avoiding graphics resource hitches allocations yes Vulkan friendly 11 Unlikely to Benefit Scenarios to Reconsider Coding to Vulkan 1.
    [Show full text]
  • Introduction to Computer Graphics with Webgl
    Introduction to Computer Graphics with WebGL Ed Angel Professor Emeritus of Computer Science Founding Director, Arts, Research, Technology and Science Laboratory University of New Mexico Angel and Shreiner: Interactive Computer Graphics 7E © Addison-Wesley 2015 1 Models and Architectures Angel and Shreiner: Interactive Computer Graphics 7E © Addison-Wesley 2015 2 Objectives • Learn the basic design of a graphics system • Introduce pipeline architecture • Examine software components for an interactive graphics system Angel and Shreiner: Interactive Computer Graphics 7E © Addison-Wesley 2015 3 Image Formation Revisited • Can we mimic the synthetic camera model to design graphics hardware software? • Application Programmer Interface (API) - Need only specify • Objects • Materials • Viewer • Lights • But how is the API implemented? Angel and Shreiner: Interactive Computer Graphics 7E © Addison-Wesley 2015 4 Physical Approaches • Ray tracing: follow rays of light from center of projection until they either are absorbed by objects or go off to infinity - Can handle global effects • Multiple reflections • Translucent objects - Slow - Must have whole data base available at all times • Radiosity: Energy based approach - Very slow Angel and Shreiner: Interactive Computer Graphics 7E © Addison-Wesley 2015 5 Practical Approach • Process objects one at a time in the order they are generated by the application - Can consider only local lighting • Pipeline architecture application display program • All steps can be implemented in hardware on the graphics
    [Show full text]
  • Opengl Install Guide
    OpenGL Install Guide Windows Install your favorite IDE. This tutorial assumes that you have Microsoft Visual Studio 6.0 (available from the CS Department Software Library as of Autumn 2004) installed on your machine. See specific IDE guides at the end of this document for more information. Install OpenGL OpenGL v1.1 software runtime is included as part of operating system for WinXP, Windows 2000, Windows 98, Windows 95 (OSR2) and Windows NT. If you think your copy is missing, the OpenGL v1.1 libraries are also available as the self- extracting archive file from the Microsoft website, via this url: http://download.microsoft.com/download/win95upg/info/1/W95/EN-US/Opengl95.exe OpenGL Libraries and header files are • opengl32.lib • glu32.lib • gl.h • glu.h Install GLUT GLUT is not normally pre-installed. You can download it from: http://www.xmission.com/~nate/glut/glut-3.7.6-bin.zip Install GLUT by following the instructions in the README file (copy and pasted here): Copy the files: 1. glut32.dll to %WinDir%\System, 2. glut32.lib to $(MSDevDir)\..\..\VC98\lib 3. glut.h to $(MSDevDir)\..\..\VC98\include\GL. Use OpenGL & GLUT in your source code 1. Start Visual C++ and create a new empty project of type “Win32 Console Application.” 2. To test your setup, add a simple GLUT program to the project like “drawCircle.cpp” from our sample programs. 3. You should only need to #include <GL/glut.h>. It includes the other necessary dependent libraries. You might need to modify our example programs to fit this requirement.
    [Show full text]
  • An Introduction to Openvg™ FTF-AUT-F0465
    An Introduction to OpenVG™ FTF-AUT-F0465 Oliver Tian | Auto FAE M A Y . 2 0 1 4 TM External Use Agenda • Trend of Graphics in Vehicle • Roadmap of Cluster • Introduction of Rainbow/Vybrid • OpenVG Scenario • Development Ecosystem • Conclusion TM External Use 1 Trend of Graphics in Vehicle TM External Use 2 The Connected Vehicle Infotainment + Communication + Security • Consumer electronics trends are dictating features in the car • Always connected, applications driven, advanced graphics • Infotainment systems becoming battleground for Auto differentiation • As more connected systems get introduced into the vehicle, the need for security is critical − Increasing external communication features (Bluetooth, TPMS, Ethernet, Wi-Fi, etc). − Future interface for vehicle-to-vehicle and vehicle-to-infrastructure. TM External Use 3 Mobility for Everyone Affordable Solutions for Emerging Markets • 100M vehicles annually forecasted before 2020, on top of motorcycle & e-bike growth • 80% of quantity growth after 2015 happening in emerging markets • Safety and emissions reduction are key for a sustainable development Source: IHS Automotive, February 2014 TM External Use 4 More, More, More for Less, Less, Less More performance, more embedded memory, more safety for less cost, less power and less development effort More • Electronic complexity • ECUs per car (50+) • MCUs per car (100+) • In-car Wi-Fi ® (7.2Mbps and 3.7Bpcs by 2017) iSuppli Less Reuse • Other markets have less critical applications • Some automotive specific challenges TM External Use 5 Today’s Car • Complex computerized control − Millions of lines of code, from multiple vendors − Dozens of distinct ECUs, from multiple vendors • Shared internal networking (e.g., CAN, FlexRay) − Increasing external communications features .
    [Show full text]
  • Portable Opengl (ES) Jamie Madill / July 31, 2019
    ANGLE Portable OpenGL (ES) Jamie Madill / July 31, 2019 ANGLE is an OpenGL driver that.. ● Translates OpenGL to native commands on multiple major OSes. ● Gives portable OpenGLby working around driver bugs. ANGLE has billions of users! ● Several popular browsers use ANGLE for Code is like a layer cake. Application Entry Points GL Validation GL Context ANGLE Front-End (State Tracking) GL Back-End Vk Back-End D3D Back-End Validation Vulkan LVL Debug Runtime Driver GL Driver Vulkan Driver D3D Driver Slicing the layers angle::Result Buffer::bufferData(Context *context, BufferBinding target, const void *data, Entry Points GLsizeiptr size, BufferUsage usage) { GL Validation GL Context ANGLE_TRY(mImpl->setData(context, target, data, size, usage)); Front-End (State Tracking) mIndexRangeCache.clear(); mState.mUsage = usage; mState.mSize = size; GL Back-End Vk Back-End D3D Back-End onStateChange(angle::SubjectMessage::SubjectChanged); return angle::Result::Continue; } Slicing the layers angle::Result BufferVk::setData(const gl::Context *context, gl::BufferBinding target, Entry Points const void *data, size_t size, gl::BufferUsage usage) GL Validation GL Context { ContextVk *contextVk = vk::GetImpl(context); Front-End (State Tracking) if (size > static_cast<size_t>(mState.getSize())) { // Release and re-create the memory and buffer. GL Back-End Vk Back-End D3D Back-End release(contextVk); VkBufferCreateInfo createInfo = { /* ... */ }; ANGLE_TRY(mBuffer.init(contextVk, createInfo, kMemoryPropertyFlags)); } if (data && size > 0) { ANGLE_TRY(setDataImpl(contextVk, data, size, 0)); } return angle::Result::Continue; } What’s next: Android ○ Vendors must supportlegacy GL drivers. ○ They also must support theVulkan API. Vendor “A” Vendor “B” Vendor “C” Vendor “D” What’s next: Android ○ Focus on high quality Vulkan drivers with GL emulation.
    [Show full text]
  • Stronger NYC Communities Organizational Digital Security Guide
    Stronger NYC Communities Organizational Digital Security Guide For Trainers and Participants Build Power - not Paranoia! NYC Stronger Communities | Toolkit 1 Creative Commons Attribution-ShareAlike 4.0 International, July 2018 This work supported by Mozilla Foundation, the NYC Mayor’s Office of Immigrant Affairs, NYC Mayor’s Office of the CTO, and Research Action Design. CREDITS Project designed and lead by Sarah Aoun and Bex Hong Hurwitz. Curriculum lead writing by Rory Allen. Workshops, activities, and worksheets were developed by Nasma Ahmed, Rory Allen, Sarah Aoun, Rebecca Chowdhury, Hadassah Damien, Harlo Holmes, Bex Hong Hurwitz, David Huerta, Palika Makam (WITNESS), Kyla Massey, Sonya Reynolds, and Xtian Rodriguez. This Guide was arranged and edited by Hadassah Damien, and designed by Fridah Oyaro, Summer 2018. More at: https://strongercommunities.info NYC Stronger Communities | Toolkit 2 Table of Contents ORGANIZATIONAL DIGITAL SECURITY GUIDE This guide provides tools and ideas to help organizational digital security workshop leaders approach the work including a full facilitator’s guide with agendas and activities; for learners find a participant guide with homework, exercises, and a resource section. 01 03 INTRODUCTION ............................................ 4 PARTICIPANT WORKBOOK ........................................ 110 • Organizational Digital Security Right Now Introduction to the Stronger Communities • Roadmap Workshop series Self-assessment: Digital • Workshop Overview Security Bingo • Series Story • How to coordinate and plan a Stronger Workshop Participant Guides Communities workshop series • Design and facilitation tools 1. Stronger NYC Communities Workshop: • Evaluate and assess Our work is political. • Handout and activity glossary 2. Stronger Communities Workshop: Our work is both individual and collective. 3. Stronger Communities Workshop: Our 02 work is about learning from and taking care of each other.
    [Show full text]