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 68901] New: wine/3DMark2001: shader generation fails
Date: Tue, 03 Sep 2013 18:24:07 +0000	[thread overview]
Message-ID: <bug-68901-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 68901
          Keywords: regression
          Assignee: dri-devel@lists.freedesktop.org
           Summary: wine/3DMark2001: shader generation fails
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: gurketsky@googlemail.com
               URL: http://www.futuremark.com/support/downloads
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

When running 3DMark2001 in wine (1.7.1), the r600 gallium driver (on RV710)
fails to generate some shaders. This is a regression:

3f67251e3d0ce61a0e7fc16de91de6fb49cad768 is the first bad commit
commit 3f67251e3d0ce61a0e7fc16de91de6fb49cad768
Author: Christian König <christian.koenig@amd.com>
Date:   Sun Mar 10 14:33:29 2013 +0100

    glsl_to_tgsi: allocate arrays separately v2

    Instead of allocating everything as temporaries, use the
    new array allocation functions.

    v2: fix bug in simplify_cmp, declare arrays on demand

    Signed-off-by: Christian König <christian.koenig@amd.com>

:040000 040000 75a734fc12e314c32a959f4111543ec518cb8a51
57eed35384ed9aadd89adfce1a075b4ad0a745cc M    src

The output when the shader generation fails is:
EE /mnt/raid0/software/mesa/git/src/gallium/drivers/r600/r600_shader.c:1886
r600_shader_from_tgsi - GPR limit exceeded - shader requires 129 registers
EE /mnt/raid0/software/mesa/git/src/gallium/drivers/r600/r600_shader.c:134
r600_pipe_shader_create - translation from TGSI failed !
EE
/mnt/raid0/software/mesa/git/src/gallium/drivers/r600/r600_state_common.c:750
r600_shader_select - Failed to build shader variant (type=0) -12
EE /mnt/raid0/software/mesa/git/src/gallium/drivers/r600/r600_shader.c:1886
r600_shader_from_tgsi - GPR limit exceeded - shader requires 129 registers
EE /mnt/raid0/software/mesa/git/src/gallium/drivers/r600/r600_shader.c:134
r600_pipe_shader_create - translation from TGSI failed !
EE
/mnt/raid0/software/mesa/git/src/gallium/drivers/r600/r600_state_common.c:750
r600_shader_select - Failed to build shader variant (type=0) -12

This is not a dupe of bug 62696 as the problem is still there with git version
6b5c802c30ada043ee31cc5e62249ff99bbc865f.

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

[-- Attachment #1.2: Type: text/html, Size: 4368 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-09-03 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 18:24 bugzilla-daemon [this message]
2019-09-18 19:05 ` [Bug 68901] wine/3DMark2001: shader generation fails 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-68901-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).