All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Marek Olšák" <maraeo@gmail.com>, "Ilia Mirkin" <imirkin@alum.mit.edu>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	"mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>
Subject: Re: [PATCH mesa v2 3/3] nouveau: codegen: LOAD: Take src swizzle into account
Date: Fri, 22 Apr 2016 09:23:43 +0200	[thread overview]
Message-ID: <5719D17F.3050503@redhat.com> (raw)
In-Reply-To: <CAAxE2A5V82mQQxC0Gif3SC=CcUv++DDaTNy4EmVgiqCkKP5inw@mail.gmail.com>

Hi,

On 22-04-16 09:08, Marek Olšák wrote:
> On Thu, Apr 21, 2016 at 7:04 PM, Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>> [+radeon folk]
>>
>> Marek, Nicolai, Bas - please have a look at the doc change and let us
>> know if you think this will cause a problem for radeon.
>>
>> Hans is solving the issue that he wants to swizzle the data loaded
>> from the image/buffer/whatever before sticking it into the dst
>> register.
>
> Is this something st/mesa needs or just nouveau? If just nouveau needs
> it, I don't see a point in updating the TGSI spec, since nouveau can
> just add the swizzle when translating from TGSI.

This is something which the llvm tgsi backend needs, which we plan to
use to add opencl support to nouveau.

 From the commit msg:

"The llvm TGSI backend uses pointers in registers and does things like:

LOAD TEMP[0].y, MEMORY[0], TEMP[0]

Expecting the data at address TEMP[0].x to get loaded to
TEMP[0].y. But this will cause the data at TEMP[0].x + 4 to be
loaded instead.

This commit adds support for a swizzle suffix for the 1st source
operand, which allows using:

LOAD TEMP[0].y, MEMORY[0].xxxx, TEMP[0]

And actually getting the desired behavior"

Regards,

Hans
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

  reply	other threads:[~2016-04-22  7:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 12:39 [PATCH mesa v2 1/3] nouveau: codegen: LOAD: Always use component 0 when getting the address Hans de Goede
2016-04-21 12:39 ` [PATCH mesa v2 2/3] nouveau: codegen: LOAD: Do not call fetchSrc(1) if the address is immediate Hans de Goede
     [not found] ` <1461242362-1281-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-04-21 12:39   ` [PATCH mesa v2 3/3] nouveau: codegen: LOAD: Take src swizzle into account Hans de Goede
2016-04-21 17:04     ` Ilia Mirkin
2016-04-22  7:08       ` Marek Olšák
2016-04-22  7:23         ` Hans de Goede [this message]
     [not found]           ` <5719D17F.3050503-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-04-22  8:37             ` Marek Olšák
     [not found]               ` <CAAxE2A5xGaAagKfFJ4rALa2rHVJ_UV3eNjXLJKwzKEp7A36ATw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-22  8:44                 ` Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5719D17F.3050503@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=imirkin@alum.mit.edu \
    --cc=maraeo@gmail.com \
    --cc=mesa-dev@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.