[Mesa-dev] soft fp64 support - main body (glsl/gallium)

[Timothy Arceri]

On 14/03/18 21:05, Timothy Arceri wrote:
> On 14/03/18 11:04, Dave Airlie wrote:
>> On 14 March 2018 at 09:54, Matt Turner <mattst88 at gmail.com> wrote:
>>> On Mon, Mar 12, 2018 at 9:24 PM, Dave Airlie <airlied at gmail.com> wrote:
>>>> This is the main code for the soft fp64 work. It's mostly Elie's
>>>> code with a bunch of changes by me.
>>>>
>>>> This patchset has all the glsl lowering code. (using float64.glsl,
>>>> yes I know checked in files are bad, but not bad enough for anyone
>>>> to have solved int64.glsl yet, so we have a precedent).
>>>
>>> Have you thought about making a NIR backend for R600?
>>
>> It would be a lot more work and way too uncertain, I reckon it's taken
>> Timothy 6 months to get radeonsi even close with nir, I don't have
>> 6 months to spend on getting r600 close, it's backend situation is a lot
>> worse than radeonsi.
> 
> I don't doubt its a lot of work, but I should note that a chuck of time 
> has been ironing out the somewhat rough state the state tracker was in 
> in spots and adding the missing stages, nir passes, nir shader cache etc.
> 
> Also as the goal was to make the NIR backend better than tgsi I did 
> spend a bunch of time working on NIR linking support and related passes 
> (added to RADV too). Oh and uniform packing the last couple of days.
> 
> Anyway I'm not trying to convince Dave as I'm sure he has a good idea of 
> the work involve. Just thought I'd mention this stuff in case anyone 
> else has considered working on NIR for r600 and are scared by Daves time 
> estimate :)

Oh and I meant to add that there is also some time overhead in making 
sure both the tgsi radeonsi backend and radv didn't break in the process 
(mostly the tgsi backend). Depending on how NIR support was added to 
r600 this may not be such an issue.