On 05/28/2014 01:57 PM, Eric Anholt wrote:
> If the shader compiled once, then we can compile it again. Compiled
> shaders almost always get used in just one program, so holding that
> compiled IR until the program is freed is just a waste of memory.
>
> On the other hand, if they are either reus
On 05/31/2014 02:39 PM, Eric Anholt wrote:
> Ian Romanick writes:
>
>> On 05/28/2014 01:57 PM, Eric Anholt wrote:
>>> If the shader compiled once, then we can compile it again. Compiled
>>> shaders almost always get used in just one program, so holding that
>>> compiled IR until the program is f
Ian Romanick writes:
> On 05/28/2014 01:57 PM, Eric Anholt wrote:
>> If the shader compiled once, then we can compile it again. Compiled
>> shaders almost always get used in just one program, so holding that
>> compiled IR until the program is freed is just a waste of memory.
>
> Would this work
On 05/28/2014 01:57 PM, Eric Anholt wrote:
> If the shader compiled once, then we can compile it again. Compiled
> shaders almost always get used in just one program, so holding that
> compiled IR until the program is freed is just a waste of memory.
Would this work with some madness like:
gl
If the shader compiled once, then we can compile it again. Compiled
shaders almost always get used in just one program, so holding that
compiled IR until the program is freed is just a waste of memory.
On the other hand, if they are either reusing shader objects to compile
multiple times, or link
