>
> Yes, NIR arrays and struct and nir_deref to deal with them but, by the
> time you get into the back-end, all the nir_derefs are gone and you're left
> with load/store messages with actual addresses (either a 64-bit memory
> address or a index+offset pair for a bound resource). Again, unless yo
Hi Abel,
On Sun, 2022-01-23 at 13:58 +0100, Abel Bernabeu wrote:
>
> That is the thing: there is already a community maintained LLVM
> backend for RISC-V and I need to see how to get value from that
> effort. And that is a very typical escenario for new architectures.
> There is already an LLVM b
On Sun, Jan 23, 2022 at 1:58 PM Abel Bernabeu
wrote:
>>
>> Yes, NIR arrays and struct and nir_deref to deal with them but, by the time
>> you get into the back-end, all the nir_derefs are gone and you're left with
>> load/store messages with actual addresses (either a 64-bit memory address or
>
On Sun, 23 Jan 2022 at 22:58, Abel Bernabeu
wrote:
>>
>> Yes, NIR arrays and struct and nir_deref to deal with them but, by the time
>> you get into the back-end, all the nir_derefs are gone and you're left with
>> load/store messages with actual addresses (either a 64-bit memory address or
>>
Dave,
Am glad for the Mesa community to support the RISC-V effort with the advice
given so far.
I hear your concerns regarding performance. I am familiar with the Larabee
case and know some of the people who worked on that. However, I am not here
to discuss what is the RISC-V strategy for graphic
On Mon, 24 Jan 2022 at 06:52, Abel Bernabeu
wrote:
>
> Dave,
>
> Am glad for the Mesa community to support the RISC-V effort with the advice
> given so far.
>
> I hear your concerns regarding performance. I am familiar with the Larabee
> case and know some of the people who worked on that. Howev
I can tease you all with the promise of SIMT and fixed function units.
In the meantime you can hear me talking about the work we do at the
Graphics and ML Special Interest Group within RISC-V:
https://www.youtube.com/watch?v=kM0lsWjqOaw
I still need to make our site a bit more useful, but here is
