[Mesa-dev] [PATCH] glsl: free interface_types and replace old hash_table uses

The util/hash_table was intended to be a fast hash table replacement for the program/hash_table see 35fd61bd99c1 and 72e55bb6888ff. This replaces some more uses of the old hash table and also destroys the interface_types hash table when _mesa_glsl_release_types() is called which wasn't previously

Re: [Mesa-dev] [PATCH] [v2] i965/chv|skl: Apply sampler bypass w/a

On Wed, Jul 8, 2015 at 5:04 PM, Ben Widawsky wrote: > Certain compressed formats require this setting. The docs don't go into much > detail as to why it's needed exactly. > > This patch introduces no piglit regressions on gen9 (bsw is untested). Note > that > the SKL "regressions" are fixed tests

Re: [Mesa-dev] [PATCH 1/3] i965: Check the INTEL_USE_NIR environment variable once at context creation

On Fri, Apr 3, 2015 at 10:04 AM, Jason Ekstrand wrote: > On Fri, Apr 3, 2015 at 9:46 AM, Matt Turner wrote: >> On Fri, Apr 3, 2015 at 1:07 AM, Jordan Justen >> wrote: >>> On 2015-04-02 20:56:15, Jason Ekstrand wrote: --- src/mesa/drivers/dri/i965/brw_context.c | 10 +- s

[Mesa-dev] [PATCH] clover: Fix bug with computing hard_event status

pipe_context::flush() can return a NULL fence if the queue is already empty, so we should not assume that an event with a NULL fence has the status of CL_QUEUED. CC: 10.6 --- src/gallium/state_trackers/clover/core/event.cpp | 7 --- src/gallium/state_trackers/clover/core/event.hpp | 1 + 2 f

[Mesa-dev] [PATCH 1/2] gallium/drivers: Add threadsafe wrappers for pipe_context v2

These wrappers can be used by state trackers to ensure threadsafe access to pipe_context objects. v2: - Don't add wrappers for pipe_screen. - Build system cleanups CC: 10.6 --- configure.ac | 1 + src/gallium/Makefile.am|

[Mesa-dev] [PATCH 2/2] clover: Use threadsafe wrappers for pipe_context v2

Events can be added to an OpenCL command queue concurrently from multiple threads, but pipe_context bjects are not threadsafe. The threadsafe wrappers protect all pipe_context function calls with a mutex, so we can safely use them with multiple threads. v2: - Don't use wrapper for pipe_screen.

<    1   2