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 27901] GLSL cos/sin functions broken on Mesa R600 driver
Date: Wed, 19 May 2010 15:58:12 -0700 (PDT)	[thread overview]
Message-ID: <20100519225812.BA4EB13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27901-502@http.bugs.freedesktop.org/>

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

--- Comment #4 from Alain Perrot <alain.perrot@gmail.com> 2010-05-19 15:58:12 PDT ---
(In reply to comment #3)
> Alain,
> 
> Okay, The patch I just posted might fix this bug. It doesn't cause any
> additional errors in piglit either.  I think its working right with
> http://github.com/jckarter/hello-gl-ch3 too. Of course I have only tested it on
> my RadeonHD 3100 and its my first attempt at r600 assembly so let me know if it
> works for you. 
> 
> Note: it could probably be done so its faster but I'm still not to sure on how
> everything works yet in the software
> 
> Conn

Thanks for your help.

Unfortunately, your patch does not fix the cos/sin functions (at least on my
Radeon HD 3870 / RV670). The hello-gl-ch3 example works better but still not as
expected, you can compare with Mesa software rendering.

I tried to play with your patch to make it work without success for now. A note
is that there may be a mistake on the last operand to the CNDGT instruction :

+    setaddrmode_PVSSRC(&(pAsm->S[2].src), ADDR_ABSOLUTE);
+    pAsm->S[1].src.rtype = DST_REG_TEMPORARY;
+    pAsm->S[1].src.reg   = tmp2;
+    setswizzle_PVSSRC(&(pAsm->S[2].src), SQ_SEL_X);

should probably be :

+    setaddrmode_PVSSRC(&(pAsm->S[2].src), ADDR_ABSOLUTE);
+    pAsm->S[2].src.rtype = DST_REG_TEMPORARY;
+    pAsm->S[2].src.reg   = tmp2;
+    setswizzle_PVSSRC(&(pAsm->S[2].src), SQ_SEL_X);

But this update does not make the cos/sin functions work.

I will try again tomorrow.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-05-19 22:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 19:09 [Bug 27901] New: GLSL cos/sin functions broken on Mesa R600 driver bugzilla-daemon
2010-05-17 22:10 ` [Bug 27901] " bugzilla-daemon
2010-05-19  2:25 ` bugzilla-daemon
2010-05-19  2:33 ` bugzilla-daemon
2010-05-19 22:58 ` bugzilla-daemon [this message]
2010-05-19 23:46   ` Conn Clark
2010-05-19 23:46 ` bugzilla-daemon
2010-05-20 19:39 ` bugzilla-daemon
2010-05-20 19:46 ` bugzilla-daemon
2010-05-20 19:48 ` bugzilla-daemon
2010-05-21  0:40 ` bugzilla-daemon
2010-05-21  1:08   ` Conn Clark
2010-05-21  1:08 ` bugzilla-daemon
2010-05-21  7:48 ` bugzilla-daemon
2010-05-21 16:32 ` bugzilla-daemon
2010-05-21 18:13 ` bugzilla-daemon
2010-05-21 18:56   ` Conn Clark
2010-05-21 18:56 ` bugzilla-daemon
2010-05-21 20:45 ` bugzilla-daemon
2010-05-21 21:04 ` bugzilla-daemon
2010-06-07 16:17 ` bugzilla-daemon
2010-06-07 16:30 ` bugzilla-daemon
2010-06-08 12:53 ` bugzilla-daemon
2010-06-08 16:09   ` Conn Clark
2010-06-08 16:09 ` bugzilla-daemon
2010-06-08 16:26 ` bugzilla-daemon
2010-06-08 16:36 ` bugzilla-daemon
2010-07-29 14:58 ` bugzilla-daemon
2010-07-29 16:12 ` bugzilla-daemon
2010-08-03 17:05 ` 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=20100519225812.BA4EB13004E@annarchy.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