From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104591] [r600g] Compute demos and pigilt tests broken on REDWOOD, works fine on JUNIPER
Date: Fri, 12 Jan 2018 02:43:44 +0000 [thread overview]
Message-ID: <bug-104591-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1179 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104591
Bug ID: 104591
Summary: [r600g] Compute demos and pigilt tests broken on
REDWOOD, works fine on JUNIPER
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: megwattt@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 136671
--> https://bugs.freedesktop.org/attachment.cgi?id=136671&action=edit
"pigilt run -t compute" left:REDWOOD right:JUNIPER
Some games and demos which use compute shaders misrender on my HD 5670
(REDWOOD), but works fine on my HD 5770 (JUNIPER). Tested with various Ogre
demos and Supertuxkart.
When running pigilt's compute tests ("pigilt run -t compute") 19 tests doesn't
pass on REDWOOD but pass on JUNIPER. The comparison between those 2 pigilt runs
is attached.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2794 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-01-12 2:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 2:43 bugzilla-daemon [this message]
2019-09-18 19:24 ` [Bug 104591] [r600g] Compute demos and pigilt tests broken on REDWOOD, works fine on JUNIPER 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-104591-502@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.