On Tue, Feb 22, 2011 at 10:08 PM, Eric Anholt <e...@anholt.net> wrote: > On Tue, 22 Feb 2011 11:57:38 -0800, Ian Romanick <i...@freedesktop.org> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 02/21/2011 02:41 PM, Eric Anholt wrote: >> > This extension allows a client to bind one context in multiple threads >> > simultaneously. It is then up to the client to manage synchronization of >> > access to the GL, just as normal multithreaded GL from multiple contexts >> > requires synchronization management to shared objects.
[snip] >> We may need to make the new behavior opt-in per-context anyway. This >> changes some very subtle and touchy GL behaviors, so some of these >> changes may have unforeseen affects on existing apps. Changing these >> things always makes me nervous. Over the years we've all independently >> discovered that MakeCurrent and SwapBuffers are like Koch snowflakes... >> there are *only* corner cases. > > GL has in the past changed things that were errors to not be errors to > extend functionality and make the GL more useful -- see, for example, > the deltas between GL_EXT_framebuffer_object to > GL_ARB_framebuffer_object, which didn't first introduce a > GL_DONT_THROW_ERRORS_FOR_LUMINANCE_FBOS knob. I don't see why we should > make the API even harder to access just to preserve an error return. The difference is race conditions galore with no defined behavior vs well defined behavior with just returning a error code. This needs to be opt in. Cheers Jakob. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
