AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
9a48bebe6a
skia2/tools/gpu/gl/interface
History
Chris Dalton 0a1923e507 Disable QCOM_tiled_rendering while we wait for test devices 
There are devices that advertise this extension but don't actually
provide the GL entrypoints. This is causing live crashes.

Bug: flutter:47164
Bug: flutter:47804
Change-Id: Idded47e8dbd4462463ad91a62b06b0df3245f0c1
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/263809
Reviewed-by: Brian Osman <brianosman@google.com>
Commit-Queue: Chris Dalton <csmartdalton@google.com>
2020-01-11 06:04:56 +00:00
..
gen_interface.go Reland "Get EGLimage functions out of GrGLInterface." 2019-05-15 19:58:45 +00:00
interface.json5 Disable QCOM_tiled_rendering while we wait for test devices 2020-01-11 06:04:56 +00:00
Makefile Reland "Generate GrGLInterface and GrGlAssembleInterface* from table" 2019-03-26 10:55:00 +00:00
README.md Reland "Generate GrGLInterface and GrGlAssembleInterface* from table" 2019-03-26 10:55:00 +00:00
templates.go Turn off -Wreturn-std-move-in-c++11 2019-08-15 17:45:58 +00:00

README.md

GrGlInterface Autogeneration

Background

At a high level, the first three steps of making a GrGLInterface (a generic way to interact with a GL-like GPU) are:

  • Assemble: Copy a set of function pointers into the struct
  • Validate: Make sure the function pointers advertised actually exist.
  • Capabilities: Compute what fast/slow paths are enabled based on the functions in the struct (GrGLCaps, for short)

Autogeneration

The first two steps have been automated with a table-based generation script located in this folder. The table is in JSON5 format (like JSON, but with comments). O

Once edited, the Assemble/Validate code can be re-generated by running make generate in this folder.