From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91808] trine1 misrender r600g
Date: Fri, 27 Apr 2018 06:48:13 +0000 [thread overview]
Message-ID: <bug-91808-502-cGUjIM0zS3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91808-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1092 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91808
--- Comment #13 from Dave Airlie <airlied@freedesktop.org> ---
Just adding some things I've tried to fix this to no avail.
use RECIP_FF/CLAMPED instead of RECIP_IEEE
use RECIPSQRT_FF/CLAMPED instead of RECIPSQRT_IEEE
use MUL/MULADD/DOT4 instead of IEEE
Split constants into DOT4, rewrote DOT4 output to go via another register.
Disable scaled 16-bit float vertices, this change the misrendering to something
worse for some reason.
I've noticed the broken drawing operations are the same vbo/ib with a different
set of constant values for VS constants 124-126, the first draw works and draws
the inside gear, the second draw to draw the outside gear fails.
I considered then it might be constant caching or vertex caching since we use
vfetch to fetch the consts, tried add more flushing between draws, tried using
uncached descriptor for constant buffer.
Nothing above has fixed it, merely logging it for my own sanity at this point.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1823 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 prev parent reply other threads:[~2018-04-27 6:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 11:24 [Bug 91808] trine1 misrender r600g bugzilla-daemon
2015-08-30 11:35 ` bugzilla-daemon
2015-08-31 3:19 ` bugzilla-daemon
2015-08-31 3:21 ` bugzilla-daemon
2015-08-31 8:50 ` bugzilla-daemon
2015-08-31 13:10 ` bugzilla-daemon
2015-09-01 6:38 ` bugzilla-daemon
2015-09-01 6:41 ` bugzilla-daemon
2015-09-01 12:30 ` bugzilla-daemon
2016-08-17 5:04 ` bugzilla-daemon
2018-03-26 17:02 ` bugzilla-daemon
2018-03-31 23:41 ` bugzilla-daemon
2018-04-21 6:04 ` bugzilla-daemon
2018-04-23 21:40 ` bugzilla-daemon
2018-04-24 6:34 ` bugzilla-daemon
2018-04-27 6:48 ` bugzilla-daemon [this message]
2018-05-09 5:45 ` bugzilla-daemon
2018-05-09 15:02 ` bugzilla-daemon
2018-05-10 1:16 ` bugzilla-daemon
2018-05-13 7:12 ` 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-91808-502-cGUjIM0zS3@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.