dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103544] Graphical glitches r600 in game this war of mine linux native
Date: Wed, 08 Nov 2017 00:25:25 +0000	[thread overview]
Message-ID: <bug-103544-502-1TfDjhuUBB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103544-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from Roland Scheidegger <sroland@vmware.com> ---
(In reply to Ilia Mirkin from comment #13)
> (In reply to Roland Scheidegger from comment #12)
> > Here's a apitrace for this (1GB, of course the corruption is only seen
> > towards the end...), should be available a week (?):
> > https://we.tl/EanuxRG7Yf
> 
> Well, this all replays fine with nouveau, even if I remove the blending
> config which makes 0*nan=0. At least I couldn't see any artifacts.
> 
> So this all points to ... sadness. Can you check if you still see artifacts
> with nosb?

Tried that, doesn't help.

I noticed some things looking questionable in the driver:
- the driver doesn't use the ieee variants consistently (e.g. muls from lerps).
There's also some inconsistencies - for r600, the comments say for non-gl usage
the ieee variant should be used for rcp, however eg/cayman will use that
anyway, and I don't think handling it differently between these drivers is done
on purpose.
- the driver uses min/max instead of min_dx10/max_dx10 (though at least the EG
ISA docs are wrong/inaccurate what they exactly do). These would kill off NaNs
(albeit I am not entirely sure if the non-dx10 version doesn't kill off NaNs
neither, given the docs aren't accurate in the first place...). I think this
probably should be changed (as far as I can tell, radeonsi also uses
effectively the dx10 versions, since llvm.min/maxnum is specified as selecting
non-nan operands, though I don't know if the backend honors it really). This
actually does help things, it removes the black holes in the fires, and the
"vertical blue stripes" (albeit the latter wasn't really in that trace). But
otherwise there's still lots of black boxes around.

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

[-- Attachment #1.2: Type: text/html, Size: 2889 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

  parent reply	other threads:[~2017-11-08  0:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 12:39 [Bug 103544] Graphical glitches r600 in game this war of mine linux native bugzilla-daemon
2017-11-02 13:27 ` bugzilla-daemon
2017-11-02 13:36 ` bugzilla-daemon
2017-11-02 14:01 ` bugzilla-daemon
2017-11-03 15:48 ` bugzilla-daemon
2017-11-04  2:48 ` bugzilla-daemon
2017-11-04  3:21 ` bugzilla-daemon
2017-11-04  6:00 ` bugzilla-daemon
2017-11-04 14:34 ` bugzilla-daemon
2017-11-04 14:49 ` bugzilla-daemon
2017-11-06  4:52 ` bugzilla-daemon
2017-11-06 20:33 ` bugzilla-daemon
2017-11-06 21:14 ` bugzilla-daemon
2017-11-07 19:20 ` bugzilla-daemon
2017-11-08  0:25 ` bugzilla-daemon [this message]
2017-11-08  0:36 ` bugzilla-daemon
2017-11-15  2:22 ` 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-103544-502-1TfDjhuUBB@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).