All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64600] r600g pyrit OpenCL issue on HD6850
Date: Thu, 31 Oct 2013 15:42:23 +0000	[thread overview]
Message-ID: <bug-64600-502-BIVPss2YRR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64600-502@http.bugs.freedesktop.org/>


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

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

Peter Wu <lekensteyn@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #21 from Peter Wu <lekensteyn@gmail.com> ---
Works now with the latest mesa and llvm. If the performance is still bad, you
are probably affected by a bad workgroup size. In that case, try Tom's
pyrit-perfs[1][2] patches on top of ac81b6f2be8779022e8641984b09118b57263128.

The second patch[2] is already upstreamed, but patch [1] does not apply on the
current master because of other changes in the area.

 [1]:
http://people.freedesktop.org/~tstellar/pyrit-perf/0001-XXX-clover-Calculate-the-optimal-work-group-size.patch
 [2]:
http://people.freedesktop.org/~tstellar/pyrit-perf/0001-radeon-llvm-Specify-the-DataLayout-when-running-opti.patch

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

[-- Attachment #1.2: Type: text/html, Size: 2737 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:[~2013-10-31 15:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 19:35 [Bug 64600] New: r600g pyrit OpenCL issue on HD6850 bugzilla-daemon
2013-05-14 23:18 ` [Bug 64600] " bugzilla-daemon
2013-09-15 15:15 ` bugzilla-daemon
2013-09-15 21:50 ` bugzilla-daemon
2013-09-17 17:53 ` bugzilla-daemon
2013-09-17 19:03 ` bugzilla-daemon
2013-09-17 19:21 ` bugzilla-daemon
2013-09-17 19:31 ` bugzilla-daemon
2013-09-17 19:42 ` bugzilla-daemon
2013-09-17 20:03 ` bugzilla-daemon
2013-09-19  1:14 ` bugzilla-daemon
2013-09-19 20:42 ` bugzilla-daemon
2013-10-10 17:58 ` bugzilla-daemon
2013-10-10 18:34 ` bugzilla-daemon
2013-10-12 22:30 ` bugzilla-daemon
2013-10-14 15:40 ` bugzilla-daemon
2013-10-14 16:16 ` bugzilla-daemon
2013-10-15  6:42 ` bugzilla-daemon
2013-10-15 22:56 ` bugzilla-daemon
2013-10-16  0:01 ` bugzilla-daemon
2013-10-16 19:58 ` bugzilla-daemon
2013-10-31 15:42 ` bugzilla-daemon [this message]

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-64600-502-BIVPss2YRR@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 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.