From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99150] Shader issue for "The Cave" comparing Mesa13 to AMDGPU-PRO
Date: Mon, 19 Dec 2016 20:11:38 +0000 [thread overview]
Message-ID: <bug-99150-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1200 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99150
Bug ID: 99150
Summary: Shader issue for "The Cave" comparing Mesa13 to
AMDGPU-PRO
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: minor
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: johnz@lunarg.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 128565
--> https://bugs.freedesktop.org/attachment.cgi?id=128565&action=edit
Image differences of "The Cave" using Mesa13 vs AMDGPU-PRO
Overview:
There are some possible shader issues when comparing screen shots of "The Cave"
with Mesa13 to AMD's AMDGPU-PRO.
Hardware and versions:
The images were captured Using the Mesa 13.0 branch and AMD's AMDGPU-PRO's
16.30 driver. These image differences were observed on both AMD's Rx470 and R9
Fury graphic cards.
Attached Images:
Attached are the captured images.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2830 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:[~2016-12-19 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 20:11 bugzilla-daemon [this message]
2016-12-20 2:37 ` [Bug 99150] Shader issue for "The Cave" comparing Mesa13 to AMDGPU-PRO bugzilla-daemon
2016-12-22 21:39 ` bugzilla-daemon
2016-12-22 21:39 ` 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-99150-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.