Re: [Mesa-dev] [PATCH 05/14] nir: update opcode definitions for different bit sizes

2016-03-16 Thread Iago Toral
On Mon, 2016-03-14 at 14:24 -0400, Connor Abbott wrote: > On Mon, Mar 14, 2016 at 2:10 PM, Jason Ekstrand wrote: (...) > >> > >> -opcode("ldexp", 0, tfloat, [0, 0], [tfloat, tint], "", """ > >> -dst = ldexpf(src0, src1); > >> +opcode("ldexp", 0, tfloat32, [0, 0], [tfloat32, tint32], "", """ > >> +

Re: [Mesa-dev] [PATCH 05/14] nir: update opcode definitions for different bit sizes

2016-03-14 Thread Connor Abbott
On Mon, Mar 14, 2016 at 2:10 PM, Jason Ekstrand wrote: > > > On Mon, Mar 7, 2016 at 12:46 AM, Samuel Iglesias Gonsálvez > wrote: >> >> From: Connor Abbott >> >> Some opcodes need explicit bitsizes, and sometimes we need to use the >> double version when constant folding. >> >> v2: fix output typ

Re: [Mesa-dev] [PATCH 05/14] nir: update opcode definitions for different bit sizes

2016-03-14 Thread Jason Ekstrand
On Mon, Mar 7, 2016 at 12:46 AM, Samuel Iglesias Gonsálvez < sigles...@igalia.com> wrote: > From: Connor Abbott > > Some opcodes need explicit bitsizes, and sometimes we need to use the > double version when constant folding. > > v2: fix output type for u2f (Iago) > > v3: do not change vecN opcod

[Mesa-dev] [PATCH 05/14] nir: update opcode definitions for different bit sizes

2016-03-07 Thread Samuel Iglesias Gonsálvez
From: Connor Abbott Some opcodes need explicit bitsizes, and sometimes we need to use the double version when constant folding. v2: fix output type for u2f (Iago) v3: do not change vecN opcodes to be float. The next commit will add infrastructure to enable 64-bit integer constant folding so