On 26 April 2018 at 18:57, Dylan Baker wrote:
> Quoting Emil Velikov (2018-04-26 10:35:50)
>> On 26 April 2018 at 18:24, Dylan Baker wrote:
>> > It turns out that the blocking target we had was hiding some race
>> > conditions in the anv driver with anv_extensions.h generation, we should
>> > fix
Dylan Baker writes:
> It turns out that the blocking target we had was hiding some race
> conditions in the anv driver with anv_extensions.h generation, we should
> fix those.
>
> CC: Scott D Phillips
> CC: Mark Janes
> Fixes: 92550d9b16d2b295bdac087f31b1fd6d0f808e02
>("meson: remove wo
Quoting Emil Velikov (2018-04-26 10:35:50)
> On 26 April 2018 at 18:24, Dylan Baker wrote:
> > It turns out that the blocking target we had was hiding some race
> > conditions in the anv driver with anv_extensions.h generation, we should
> > fix those.
> >
> anv_entrypoints[0] is the first output
On 26 April 2018 at 18:24, Dylan Baker wrote:
> It turns out that the blocking target we had was hiding some race
> conditions in the anv driver with anv_extensions.h generation, we should
> fix those.
>
anv_entrypoints[0] is the first output of the anv_entrypoints custom_target.
Aka it's effectiv
It turns out that the blocking target we had was hiding some race
conditions in the anv driver with anv_extensions.h generation, we should
fix those.
CC: Scott D Phillips
CC: Mark Janes
Fixes: 92550d9b16d2b295bdac087f31b1fd6d0f808e02
("meson: remove workaround for custom target creating .
