On Thu, Apr 2, 2015 at 3:19 PM, Connor Abbott wrote:
> On Thu, Apr 2, 2015 at 1:32 PM, Rob Clark wrote:
>> On Thu, Apr 2, 2015 at 1:24 PM, Jason Ekstrand wrote:
>>> On Thu, Apr 2, 2015 at 1:20 AM, Kenneth Graunke
>>> wrote:
On Wednesday, April 01, 2015 07:22:40 PM Connor Abbott wrote:
>>>
On Thu, Apr 2, 2015 at 1:32 PM, Rob Clark wrote:
> On Thu, Apr 2, 2015 at 1:24 PM, Jason Ekstrand wrote:
>> On Thu, Apr 2, 2015 at 1:20 AM, Kenneth Graunke
>> wrote:
>>> On Wednesday, April 01, 2015 07:22:40 PM Connor Abbott wrote:
I think it might be better here if we had a callback that
On Thu, Apr 2, 2015 at 1:24 PM, Jason Ekstrand wrote:
> On Thu, Apr 2, 2015 at 1:20 AM, Kenneth Graunke wrote:
>> On Wednesday, April 01, 2015 07:22:40 PM Connor Abbott wrote:
>>> I think it might be better here if we had a callback that backends can
>>> fill in that tells you when an instruction
On Thu, Apr 2, 2015 at 1:20 AM, Kenneth Graunke wrote:
> On Wednesday, April 01, 2015 07:22:40 PM Connor Abbott wrote:
>> I think it might be better here if we had a callback that backends can
>> fill in that tells you when an instruction can be pulled out by the
>> sel peephole. As Jason noted, y
On Wednesday, April 01, 2015 07:22:40 PM Connor Abbott wrote:
> I think it might be better here if we had a callback that backends can
> fill in that tells you when an instruction can be pulled out by the
> sel peephole. As Jason noted, you won't be able to do this for
> everything (notably, output
On Wed, Apr 1, 2015 at 4:20 PM, Rob Clark wrote:
> On Wed, Apr 1, 2015 at 6:56 PM, Jason Ekstrand wrote:
>> On Tue, Mar 31, 2015 at 3:57 PM, Rob Clark wrote:
>>> From: Rob Clark
>>>
>>> Freedreno and vc4 want this behavior for the time being (until we have
>>> real flow control). Even after th
I think it might be better here if we had a callback that backends can
fill in that tells you when an instruction can be pulled out by the
sel peephole. As Jason noted, you won't be able to do this for
everything (notably, output writes and variable writes) and we'll
probably need special handling
On Wed, Apr 1, 2015 at 6:56 PM, Jason Ekstrand wrote:
> On Tue, Mar 31, 2015 at 3:57 PM, Rob Clark wrote:
>> From: Rob Clark
>>
>> Freedreno and vc4 want this behavior for the time being (until we have
>> real flow control). Even after that, we probably want to turn this into
>> some sort of dr
On Tue, Mar 31, 2015 at 3:57 PM, Rob Clark wrote:
> From: Rob Clark
>
> Freedreno and vc4 want this behavior for the time being (until we have
> real flow control). Even after that, we probably want to turn this into
> some sort of driver tunable threshold, since for at least some hardware,
> re
Rob Clark writes:
> From: Rob Clark
>
> Freedreno and vc4 want this behavior for the time being (until we have
> real flow control). Even after that, we probably want to turn this into
> some sort of driver tunable threshold, since for at least some hardware,
> reasonably large if/else is best
On Tue, Mar 31, 2015 at 7:08 PM, Matt Turner wrote:
> On Tue, Mar 31, 2015 at 3:57 PM, Rob Clark wrote:
>> From: Rob Clark
>>
>> Freedreno and vc4 want this behavior for the time being (until we have
>> real flow control). Even after that, we probably want to turn this into
>> some sort of driv
On Tue, Mar 31, 2015 at 3:57 PM, Rob Clark wrote:
> From: Rob Clark
>
> Freedreno and vc4 want this behavior for the time being (until we have
> real flow control). Even after that, we probably want to turn this into
> some sort of driver tunable threshold, since for at least some hardware,
> re
From: Rob Clark
Freedreno and vc4 want this behavior for the time being (until we have
real flow control). Even after that, we probably want to turn this into
some sort of driver tunable threshold, since for at least some hardware,
reasonably large if/else is best flattend rather than having div
13 matches
Mail list logo
