On Sat, Jan 6, 2018 at 1:34 AM, Kenneth Graunke wrote:
> On Thursday, January 4, 2018 11:56:44 AM PST Jason Ekstrand wrote:
>> On January 4, 2018 12:51:15 Karol Herbst wrote:
>>
>> > On Thu, Jan 4, 2018 at 7:06 PM, Ilia Mirkin
On Thursday, January 4, 2018 11:56:44 AM PST Jason Ekstrand wrote:
> On January 4, 2018 12:51:15 Karol Herbst wrote:
>
> > On Thu, Jan 4, 2018 at 7:06 PM, Ilia Mirkin wrote:
> >> On Thu, Jan 4, 2018 at 10:01 AM, Karol Herbst wrote:
On January 4, 2018 14:21:17 Ilia Mirkin wrote:
On Thu, Jan 4, 2018 at 3:07 PM, Jason Ekstrand wrote:
On January 4, 2018 14:02:25 Ilia Mirkin wrote:
On Thu, Jan 4, 2018 at 2:57 PM, Karol Herbst wrote:
On Thu, Jan 4, 2018 at 3:07 PM, Jason Ekstrand wrote:
> On January 4, 2018 14:02:25 Ilia Mirkin wrote:
>
>> On Thu, Jan 4, 2018 at 2:57 PM, Karol Herbst wrote:
>>>
>>> On Thu, Jan 4, 2018 at 8:56 PM, Jason Ekstrand
On January 4, 2018 14:02:25 Ilia Mirkin wrote:
On Thu, Jan 4, 2018 at 2:57 PM, Karol Herbst wrote:
On Thu, Jan 4, 2018 at 8:56 PM, Jason Ekstrand wrote:
What is the nature of the immediate problem? We may have a similar
On Thu, Jan 4, 2018 at 2:57 PM, Karol Herbst wrote:
> On Thu, Jan 4, 2018 at 8:56 PM, Jason Ekstrand wrote:
>> What is the nature of the immediate problem? We may have a similar issue.
>
> we don't do rescheduling, so all the immediates are at the top
On January 4, 2018 13:58:00 Karol Herbst wrote:
On Thu, Jan 4, 2018 at 8:56 PM, Jason Ekstrand wrote:
On January 4, 2018 12:51:15 Karol Herbst wrote:
On Thu, Jan 4, 2018 at 7:06 PM, Ilia Mirkin wrote:
On Thu, Jan 4, 2018 at 8:56 PM, Jason Ekstrand wrote:
> On January 4, 2018 12:51:15 Karol Herbst wrote:
>
>> On Thu, Jan 4, 2018 at 7:06 PM, Ilia Mirkin wrote:
>>>
>>> On Thu, Jan 4, 2018 at 10:01 AM, Karol Herbst
On January 4, 2018 12:51:15 Karol Herbst wrote:
On Thu, Jan 4, 2018 at 7:06 PM, Ilia Mirkin wrote:
On Thu, Jan 4, 2018 at 10:01 AM, Karol Herbst wrote:
significant changes to last series:
* arb_gpu_shader5 interpolateat* (those
On Thu, Jan 4, 2018 at 7:06 PM, Ilia Mirkin wrote:
> On Thu, Jan 4, 2018 at 10:01 AM, Karol Herbst wrote:
>> significant changes to last series:
>> * arb_gpu_shader5 interpolateat* (those nir ops don't map well to nvir)
>> no good plan on how to
On Thu, Jan 4, 2018 at 10:01 AM, Karol Herbst wrote:
> significant changes to last series:
> * arb_gpu_shader5 interpolateat* (those nir ops don't map well to nvir)
> no good plan on how to properly implement those
What's the issue? They should map as well as the TGSI ones.
On January 4, 2018 11:50:12 Karol Herbst wrote:
On Thu, Jan 4, 2018 at 6:39 PM, Jason Ekstrand wrote:
I'm fairly pleased that you were able to get this far with only 3k lines.
How much is that compared to your TGSI consumer?
around 4,3k, but keep
On Thu, Jan 4, 2018 at 6:39 PM, Jason Ekstrand wrote:
> I'm fairly pleased that you were able to get this far with only 3k lines.
> How much is that compared to your TGSI consumer?
>
>
around 4,3k, but keep in mind, that we really only want to convert
things here and all
I'm fairly pleased that you were able to get this far with only 3k lines.
How much is that compared to your TGSI consumer?
On January 4, 2018 09:02:24 Karol Herbst wrote:
significant changes to last series:
* support for geometry, tessellation and compute shaders
*
significant changes to last series:
* support for geometry, tessellation and compute shaders
* support for more intrinsics and operations
* lot of fixes for 64 bit types
* NV50_PROG_USE_NIR=1 can be used to enable NIR for non debug builds
There are some outstanding issues triggered by having 64
15 matches
Mail list logo