From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104602] [apitrace] Graphical artifacts in Civilization VI on RX Vega
Date: Thu, 01 Aug 2019 14:09:56 +0000 [thread overview]
Message-ID: <bug-104602-502-4WW38XEEnW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104602-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104602
--- Comment #20 from Connor Abbott <cwabbott0@gmail.com> ---
I wanted to make sure that improving the NIR path to reach parity with TGSI in
local variable handling wouldn't break things, so I investigated this a bit
more. It seems this is triggered by the fact that on Vega the TGSI path always
uses scratch, even for smaller local arrays. This bloats the scratch space used
by the VS in question. There are three back-to-back draw calls with this VS
(used to build up the map), each using scratch, and it seems that radeonsi
doesn't properly wait for each call to be done before starting the next and
reuses the same scratch buffer, resulting in the threads from one draw call
overwriting the scratch of the previous call. Hacking
si_update_spi_tmpring_size() to always allocate a new scratch buffer "fixes"
the black triangles.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1844 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-01 14:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 15:58 [Bug 104602] Graphical artifacts in Civilization VI on RX Vega bugzilla-daemon
2018-01-20 13:04 ` bugzilla-daemon
2018-01-20 13:10 ` bugzilla-daemon
2018-01-22 6:33 ` bugzilla-daemon
2018-01-24 2:37 ` [Bug 104602] [apitrace] " bugzilla-daemon
2018-03-18 22:44 ` bugzilla-daemon
2018-03-18 22:47 ` bugzilla-daemon
2018-04-09 12:15 ` bugzilla-daemon
2018-04-09 13:26 ` bugzilla-daemon
2018-08-13 14:19 ` bugzilla-daemon
2018-09-16 16:11 ` bugzilla-daemon
2018-09-21 3:28 ` bugzilla-daemon
2018-09-21 10:36 ` bugzilla-daemon
2018-09-21 12:25 ` bugzilla-daemon
2018-09-22 1:18 ` bugzilla-daemon
2018-10-05 10:50 ` bugzilla-daemon
2018-10-05 10:57 ` bugzilla-daemon
2018-11-01 0:30 ` bugzilla-daemon
2018-11-01 0:37 ` bugzilla-daemon
2018-11-01 6:39 ` bugzilla-daemon
2018-12-01 11:26 ` bugzilla-daemon
2019-03-12 10:44 ` bugzilla-daemon
2019-08-01 14:09 ` bugzilla-daemon [this message]
2019-08-01 14:13 ` bugzilla-daemon
2019-08-16 18:17 ` bugzilla-daemon
2019-08-19 19:28 ` bugzilla-daemon
2019-08-19 23:06 ` bugzilla-daemon
2019-08-20 4:13 ` bugzilla-daemon
2019-08-23 3:50 ` 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-104602-502-4WW38XEEnW@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.