On Tuesday, January 14, 2020, Jacob Lifshay
wrote:
> On Mon, Jan 13, 2020 at 9:39 AM Jason Ekstrand
> wrote:
> >
> > On Mon, Jan 13, 2020 at 11:27 AM Luke Kenneth Casson Leighton <
> l...@lkcl.net> wrote:
> >> jason i'd be interested to hear your thoughts on what jacob wrote, does
> it alleviate
On Mon, Jan 13, 2020 at 9:39 AM Jason Ekstrand wrote:
>
> On Mon, Jan 13, 2020 at 11:27 AM Luke Kenneth Casson Leighton
> wrote:
>> jason i'd be interested to hear your thoughts on what jacob wrote, does it
>> alleviate your concerns, (we're not designing hardware specifically around
>> vec2/3
On Mon, Jan 13, 2020 at 11:27 AM Luke Kenneth Casson Leighton
wrote:
>
>
> On Monday, January 13, 2020, Jacob Lifshay
> wrote:
>
>> On Thu, Jan 9, 2020 at 3:56 AM Luke Kenneth Casson Leighton
>> wrote:
>> >
>>
>> > jacob perhaps you could clarify, here?
>>
>> So the major issue with the approac
On Monday, January 13, 2020, Jacob Lifshay wrote:
> On Thu, Jan 9, 2020 at 3:56 AM Luke Kenneth Casson Leighton
> wrote:
> >
>
> > jacob perhaps you could clarify, here?
>
> So the major issue with the approach AMDGPU took where the SIMT to
> predicated vector translation is done by the LLVM bac
On Thu, Jan 9, 2020 at 3:56 AM Luke Kenneth Casson Leighton
wrote:
>
> On 1/9/20, Jason Ekstrand wrote:
> >> 2. as a flexible Vector Processor, soft-programmable, then over time if
> >> the industry moves to dropping vec4, so can we.
> >>
> >
> > That's very nice. My primary reason for sending t
