All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97988] [radeonsi] playing back videos with VDPAU exhibits deinterlacing/anti-aliasing issues not visible with VA-API
Date: Sat, 01 Oct 2016 14:38:46 +0000	[thread overview]
Message-ID: <bug-97988-502-NvhR9evdPh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97988-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from Grigori Goronzy <greg@chown.ath.cx> ---
Created attachment 126946
  --> https://bugs.freedesktop.org/attachment.cgi?id=126946&action=edit
Weave shader dumps

It looks like LLVM miscompiles the weave fragment shader due to the changes to
descriptor loading. See the attached file. With these changes, LLVM generates
some really odd looking and inefficient code in this case, and the two sample
instructions are somehow folded together, which cannot possibly work.

Someone proficient in LLVM can probably figure out what is going wrong.

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

[-- Attachment #1.2: Type: text/html, Size: 1731 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:[~2016-10-01 14:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 14:35 [Bug 97988] [radeonsi] playing back videos with VDPAU exhibits deinterlacing/anti-aliasing issues not visible with VA-API bugzilla-daemon
2016-09-30 14:36 ` bugzilla-daemon
2016-09-30 14:37 ` bugzilla-daemon
2016-09-30 14:43 ` bugzilla-daemon
2016-09-30 14:44 ` bugzilla-daemon
2016-09-30 17:48 ` bugzilla-daemon
2016-09-30 18:55 ` bugzilla-daemon
2016-09-30 20:48 ` bugzilla-daemon
2016-09-30 22:58 ` bugzilla-daemon
2016-09-30 23:34 ` bugzilla-daemon
2016-10-01 14:38 ` bugzilla-daemon [this message]
2016-10-01 18:41 ` bugzilla-daemon
2016-10-03 17:29 ` bugzilla-daemon
2016-10-03 17:55 ` bugzilla-daemon
2016-10-04 12:27 ` bugzilla-daemon
2016-10-04 15:40 ` bugzilla-daemon
2016-10-04 16:01 ` bugzilla-daemon
2016-10-25  9:46 ` bugzilla-daemon
2016-10-25 10:19 ` bugzilla-daemon
2016-10-25 12:46 ` bugzilla-daemon
2016-11-07 11:10 ` bugzilla-daemon
2016-11-07 11:38 ` bugzilla-daemon
2016-11-07 13:40 ` bugzilla-daemon
2016-11-07 14:20 ` bugzilla-daemon
2016-11-07 14:58 ` bugzilla-daemon
2016-11-07 15:09 ` bugzilla-daemon
2016-11-11 21:17 ` bugzilla-daemon
2017-02-06 12:35 ` bugzilla-daemon
2017-02-06 13:01 ` bugzilla-daemon
2017-03-05 20:09 ` bugzilla-daemon
2017-03-15 13:33 ` 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-97988-502-NvhR9evdPh@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.