dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85376] Dolphin emulator has bad colors
Date: Tue, 11 Nov 2014 20:33:50 +0000	[thread overview]
Message-ID: <bug-85376-502-aOR5wtemaj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85376-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1296 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=85376

--- Comment #10 from Ilia Mirkin <imirkin@alum.mit.edu> ---
Some observations (from IRC, edited):

In shader 21 (from attachment 109303), we see the following:

<imirkin_> MULLO_INT          R5.x,  [0x00000046 9.80909e-44].x, PV.x
<imirkin_> MULLO_INT          R5.y,  [0x00000078 1.68156e-43].x, PV.x
<imirkin_> that seems wrong
<imirkin_> the second PV.x uses the newly computed R5.x, no?
<imirkin_> instead of the previous R5.x before the mul happened
<imirkin_> so the 2nd and 3rd components get the compounded multiplication
factor of .x and the respective .y and .z factor
<tstellar> Starting with the R5.x value returned by the ADD_INT, the
caluclation is: R5.y = ((R5.x *46) * 78); R5.z = (R5.x * 46) * 0xc8
<imirkin_>   6: UMUL TEMP[1].xyz, IMM[0].yzww, TEMP[1].xxxx
<imirkin_> i'm guessing the thing that splits it up into 3 instructions forgets
that it's overwriting the source
<imirkin_> cayman_mul_int_instr
<imirkin_> cayman-specific, and doesn't do the tmp register dance

vs the "regular" umul implementation (op2_trans) which will use a temp register
if the dst mask has multiple dests. I wonder if all the cayman_* emit functions
need this treatment.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2309 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-11-11 20:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 17:48 [Bug 85376] New: Dolphin emulator has bad colors bugzilla-daemon
2014-11-10 16:10 ` [Bug 85376] " bugzilla-daemon
2014-11-10 17:04 ` bugzilla-daemon
2014-11-10 17:08 ` bugzilla-daemon
2014-11-10 17:48 ` bugzilla-daemon
2014-11-10 19:25 ` bugzilla-daemon
2014-11-10 19:58 ` bugzilla-daemon
2014-11-10 20:01 ` bugzilla-daemon
2014-11-11 17:23 ` bugzilla-daemon
2014-11-11 19:05 ` bugzilla-daemon
2014-11-11 20:33 ` bugzilla-daemon [this message]
2014-11-11 21:31 ` bugzilla-daemon
2014-11-12 21:15 ` bugzilla-daemon
2014-11-14 18:06 ` bugzilla-daemon
2014-11-18  0:38 ` bugzilla-daemon
2014-11-20  2:49 ` bugzilla-daemon
2014-11-22  7:49 ` bugzilla-daemon
2014-11-22  7:51 ` bugzilla-daemon
2014-11-22  7:52 ` bugzilla-daemon
2014-11-22 15:11 ` bugzilla-daemon
2014-11-23  3:00 ` bugzilla-daemon

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=bug-85376-502-aOR5wtemaj@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox