On Mon, 2015-11-09 at 12:27 -0500, Connor Abbott wrote:
> On Mon, Nov 9, 2015 at 10:41 AM, Jason Ekstrand wrote:
> >
> > On Nov 9, 2015 7:24 AM, "Connor Abbott" wrote:
> >>
> >> On Mon, Nov 9, 2015 at 6:55 AM, Iago Toral wrote:
> >> > Hi,
> >> >
> >> > Currently, NIR defines vecN operations as u
On Mon, Nov 9, 2015 at 10:41 AM, Jason Ekstrand wrote:
>
> On Nov 9, 2015 7:24 AM, "Connor Abbott" wrote:
>>
>> On Mon, Nov 9, 2015 at 6:55 AM, Iago Toral wrote:
>> > Hi,
>> >
>> > Currently, NIR defines vecN operations as unsigned (integer). The fp64
>> > patches from Connor change this to floa
On Nov 9, 2015 7:24 AM, "Connor Abbott" wrote:
>
> On Mon, Nov 9, 2015 at 6:55 AM, Iago Toral wrote:
> > Hi,
> >
> > Currently, NIR defines vecN operations as unsigned (integer). The fp64
> > patches from Connor change this to float (I guess because we need to
> > know the case where we are packi
On Mon, Nov 9, 2015 at 6:55 AM, Iago Toral wrote:
> Hi,
>
> Currently, NIR defines vecN operations as unsigned (integer). The fp64
> patches from Connor change this to float (I guess because we need to
> know the case where we are packing vectors of 64-bit floats). However,
> this makes it so that
2015-11-09 12:55 GMT+01:00 Iago Toral :
> Hi,
>
> Currently, NIR defines vecN operations as unsigned (integer). The fp64
> patches from Connor change this to float (I guess because we need to
> know the case where we are packing vectors of 64-bit floats). However,
> this makes it so that nir_lower
