Re: [Mesa-dev] ARB_cull_distance (final?) and llvmpipe support

2016-05-13 Thread Kristian Høgsberg Kristensen
Dave Airlie writes: > This is hopefully the final posting for this series, I've gotten > the lowering pass to look like I wanted, which is to say it lowers > to vec4[2]. > > TGSI then uses the CLIPDIST semantic and the two properties to > workout what is what. This means the CULLDIST semantic is

Re: [Mesa-dev] ARB_cull_distance (final?) and llvmpipe support

2016-05-13 Thread Dave Airlie
On 13 May 2016 at 21:45, Tobias Klausmann wrote: > Hi Dave, > > i was not aware you are working on this actively as well, i had a series > posted 5 days ago which got some critics and reviews [1]. The most important > points where: I wasn't really, then krh asked my how it worked and when I read

Re: [Mesa-dev] ARB_cull_distance (final?) and llvmpipe support

2016-05-13 Thread Tobias Klausmann
Hi Dave, i was not aware you are working on this actively as well, i had a series posted 5 days ago which got some critics and reviews [1]. The most important points where: 1. split functional change and renaming of the lowering pass [Ian] 2. check max clip/cull array sizes in link_shaders f

[Mesa-dev] ARB_cull_distance (final?) and llvmpipe support

2016-05-12 Thread Dave Airlie
This is hopefully the final posting for this series, I've gotten the lowering pass to look like I wanted, which is to say it lowers to vec4[2]. TGSI then uses the CLIPDIST semantic and the two properties to workout what is what. This means the CULLDIST semantic is no longer required. So I've ripp