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 99850] Tessellation bug on Carrizo
Date: Fri, 17 Feb 2017 15:32:28 +0000	[thread overview]
Message-ID: <bug-99850-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 99850
           Summary: Tessellation bug on Carrizo
           Product: Mesa
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: tom.stdenis@amd.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 129692
  --> https://bugs.freedesktop.org/attachment.cgi?id=129692&action=edit
carrizo run with HEAD

Tessellation is broken on Carrizo (A12-9800) hardware and apparently has been
for a while.  The offending commit is 

commit a4e2146a9d24592ed7e3bf778e3c21c6cfb89330
Author: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Date:   Mon May 2 14:55:52 2016 +0200

    radeonsi: Use buffer loads and stores for passing data from TCS to TES.

    We always try to use 4-component loads, as LLVM does not combine loads
    and they bypass the L1 cache.

    We can't use a similar strategy for stores and this is especially
    notable with the tess factors, as they are often set with separate
    MOV's per component in the TGSI.

    We keep storing to LDS and the LDS space, so we can load the outputs
    later, either due to the shader, of for wrting the tess factors.

    Signed-off-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
    Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>
    Reviewed-by: Marek Olšák <marek.olsak@amd.com>

I found it via running Unigine-Heaven with tessellation enabled.

The bug doesn't occur on other VI hardware (Polaris10, FIJI).

I can confirm that the HEAD~ commit leads to spec/arb_tessellation_shader/*
tests (in piglit) passing compared to running with HEAD.

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

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

             reply	other threads:[~2017-02-17 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 15:32 bugzilla-daemon [this message]
2017-02-17 15:33 ` [Bug 99850] Tessellation bug on Carrizo bugzilla-daemon
2017-02-17 17:53 ` bugzilla-daemon
2017-02-20  5:58 ` bugzilla-daemon
2017-02-22 17:11 ` bugzilla-daemon
2017-02-22 17:14 ` bugzilla-daemon
2017-02-22 17:15 ` bugzilla-daemon
2017-02-22 17:20 ` bugzilla-daemon
2017-02-22 17:28 ` bugzilla-daemon
2017-02-22 18:14 ` bugzilla-daemon
2017-02-23  1:20 ` bugzilla-daemon
2017-02-23 10:34 ` bugzilla-daemon
2017-02-28 15: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-99850-502@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).