From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99349] Failed to build shader (translation from TGSI)
Date: Wed, 24 May 2017 13:10:43 +0000 [thread overview]
Message-ID: <bug-99349-502-tUKm8GsK7X@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99349-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99349
--- Comment #3 from Gert Wollny <gw.fossdev@gmail.com> ---
I've had the same error output when I was playing with the Unreal Editor with
an HD6850 (BARTS) using the latest mesa-git.
In order to track it down I added some debugging to mesa and could get the
following trace that leads to the error:
r600/r600_asm.c:615
check_and_set_bank_swizzle - Couldn't find a working swizzle
drivers/r600/r600_shader.c:3975
tgsi_op2_s - Error in tgsi_op2_s, i = 3, r600_bytecode_add_alu returned -1
r600/r600_shader.c:3332
r600_shader_from_tgsi - Failed to build shader at ctx.inst_info->process,
chip class: 6, opcode: 7 result: -1
Since I added output for every "return -1" in r600/r600_asm.c I also get a lots
of other messages, but I guess that these are normal.
Debugging the code I also found that check_and_set_bank_swizzle exiting with
"Couldn't find a working swizzle" is not necessarily an error, which means that
I'm now a bit lost, because I'm not sure about how continue debugging this
problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1973 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
next prev parent reply other threads:[~2017-05-24 13:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 17:24 [Bug 99349] Failed to build shader (translation from TGSI) bugzilla-daemon
2017-01-10 17:44 ` bugzilla-daemon
2017-05-17 6:45 ` bugzilla-daemon
2017-05-24 13:10 ` bugzilla-daemon [this message]
2017-05-24 14:56 ` bugzilla-daemon
2017-05-25 8:10 ` bugzilla-daemon
2017-05-25 9:32 ` bugzilla-daemon
2017-05-26 9:01 ` bugzilla-daemon
2017-05-26 9:03 ` bugzilla-daemon
2017-05-26 13:31 ` bugzilla-daemon
2017-05-26 20:24 ` bugzilla-daemon
2017-05-29 13:28 ` bugzilla-daemon
2017-06-02 17:55 ` bugzilla-daemon
2017-06-25 22:29 ` bugzilla-daemon
2017-06-26 6:03 ` bugzilla-daemon
2017-06-26 13:41 ` bugzilla-daemon
2017-07-11 23:07 ` bugzilla-daemon
2017-07-16 21:17 ` bugzilla-daemon
2017-09-08 5:56 ` bugzilla-daemon
2017-09-08 11:05 ` bugzilla-daemon
2018-03-26 13:13 ` bugzilla-daemon
2018-03-26 18:26 ` 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-99349-502-tUKm8GsK7X@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).