diff options
author | Ian Romanick <[email protected]> | 2015-11-12 09:37:27 -0800 |
---|---|---|
committer | Ian Romanick <[email protected]> | 2016-02-10 10:59:55 -0800 |
commit | 0ecc9d907e6a76367ddf1879d3083c794337a8b5 (patch) | |
tree | 115110ad4f46e922995867988941a8b2ecf61288 /.travis.yml | |
parent | 3aeff21fbfb33197538a30871dc054064dc0ff33 (diff) |
meta/decompress: Don't pollute the renderbuffer namespace
tl;dr: For many types of GL object, we can *NEVER* use the Gen function.
In OpenGL ES (all versions!) and OpenGL compatibility profile,
applications don't have to call Gen functions. The GL spec is very
clear about how you can mix-and-match generated names and non-generated
names: you can use any name you want for a particular object type until
you call the Gen function for that object type.
Here's the problem scenario:
- Application calls a meta function that generates a name. The first
Gen will probably return 1.
- Application decides to use the same name for an object of the same
type without calling Gen. Many demo programs use names 1, 2, 3,
etc. without calling Gen.
- Application calls the meta function again, and the meta function
replaces the data. The application's data is lost, and the app
fails. Have fun debugging that.
Fixes piglit 'object-namespace-pollution glGetTexImage-compressed
renderbuffer' test.
Signed-off-by: Ian Romanick <[email protected]>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92363
Reviewed-by: Anuj Phogat <[email protected]>
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions