On Wed, Apr 1, 2015 at 10:51 PM, Kenneth Graunke wrote:
> On Wednesday, April 01, 2015 05:54:29 PM Jason Ekstrand wrote:
>> On Sat, Mar 28, 2015 at 2:28 PM, Kenneth Graunke
>> wrote:
>> > This pass performs a mark and sweep pass over a nir_shader's associated
>> > memory - anything still connect
On Wednesday, April 01, 2015 05:54:29 PM Jason Ekstrand wrote:
> On Sat, Mar 28, 2015 at 2:28 PM, Kenneth Graunke
> wrote:
> > This pass performs a mark and sweep pass over a nir_shader's associated
> > memory - anything still connected to the program will be kept, and any
> > dead memory we drop
On Sat, Mar 28, 2015 at 2:28 PM, Kenneth Graunke wrote:
> This pass performs a mark and sweep pass over a nir_shader's associated
> memory - anything still connected to the program will be kept, and any
> dead memory we dropped on the floor will be freed.
>
> The expectation is that this will be c
Two comments at the moment.
1) s/sweep/steal/
2) I think I'll have more comments and would like you to wait for me to get
a chance to look through it before pushing.
--Jason
On Mar 28, 2015 4:29 PM, "Kenneth Graunke" wrote:
> This pass performs a mark and sweep pass over a nir_shader's associate
This pass performs a mark and sweep pass over a nir_shader's associated
memory - anything still connected to the program will be kept, and any
dead memory we dropped on the floor will be freed.
The expectation is that this will be called when finished building and
optimizing the shader. However,
