On Thursday, April 28, 2016 1:40:35 PM PDT Antia Puentes wrote: > From: "Juan A. Suarez Romero" <jasua...@igalia.com> > > VS Thread Payload handles attributes in URB as vec4, no matter if they > are actually single or double precision. > > So with double-precision types, value ends up in the registers split in > 32bits chunks, in different positions. > > We need to shuffle the chunks to get the doubles correctly.
Are you saying that it shows up as
high0 high1 high2 high3 low0 low1 low2 low3
rather than
high0 low0 high1 low1 high2 low2 high3 low3
...? That's kind of strange...
Is this documented somewhere, or did you just have to figure it out?
I see things saying "up to 4 32-bit values", but not much explanation
about what happens with R64.*PASSTHRU...
> ---
> src/mesa/drivers/dri/i965/brw_fs_nir.cpp | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/src/mesa/drivers/dri/i965/brw_fs_nir.cpp b/src/mesa/drivers/
dri/i965/brw_fs_nir.cpp
> index 0ff3eaf..4362308 100644
> --- a/src/mesa/drivers/dri/i965/brw_fs_nir.cpp
> +++ b/src/mesa/drivers/dri/i965/brw_fs_nir.cpp
> @@ -3173,6 +3173,12 @@ fs_visitor::nir_emit_intrinsic(const fs_builder &bld,
nir_intrinsic_instr *instr
> for (unsigned j = 0; j < instr->num_components; j++) {
> bld.MOV(offset(dest, bld, j), offset(src, bld, j));
> }
> + if (type_sz(src.type) == 8)
> + SHUFFLE_32BIT_LOAD_RESULT_TO_64BIT_DATA(bld,
> + offset(dest, bld, 0),
> + offset(dest, bld, 0),
> + instr->num_components);
> +
> break;
> }
>
>
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
