dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104190] Artifacts in CSGO map de_cache when shader level is "high" or "very high (default)"
Date: Sun, 10 Dec 2017 11:30:34 +0000	[thread overview]
Message-ID: <bug-104190-502-yiQwmxtP5m@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104190-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Kristian Nyborg Dahl <krdahl@gmail.com> ---
This was kisak-valve's comment on their github: 

"Hello @Heis, on my AMD test box, mesa 17.2.6 built against llvm 5.0.0 is
affected, while llvm 4.0.1 is not affected.

This should also be brought to the attention of your driver vendor if it has
not been already."

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

[-- Attachment #1.2: Type: text/html, Size: 1380 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-12-10 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 11:28 [Bug 104190] Artifacts in CSGO map de_cache when shader level is "high" or "very high (default)" bugzilla-daemon
2017-12-10 11:29 ` bugzilla-daemon
2017-12-10 11:30 ` bugzilla-daemon [this message]
2017-12-10 19:58 ` bugzilla-daemon
2018-01-31 20:35 ` bugzilla-daemon
2018-04-02 10:43 ` bugzilla-daemon
2018-04-02 12:46 ` bugzilla-daemon
2018-04-12  5:37 ` bugzilla-daemon
2018-04-12  9:59 ` 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-104190-502-yiQwmxtP5m@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