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 50338] r600g: EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed !
Date: Sat, 26 May 2012 10:11:52 +0000	[thread overview]
Message-ID: <bug-50338-502-Luwu3iHDTQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-50338-502@http.bugs.freedesktop.org/>

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

--- Comment #3 from Vadim Girlin <ptpzz@yandex.ru> 2012-05-26 03:11:52 PDT ---
(In reply to comment #2)

> The problem is probably still that there are too many registers, except that
> message is no longer printed.

Yes, you are right. I think the message is not printed because the build fails
before that check - register count is checked when the shader is built, to get
the exact number with additional temporary registers etc. We can do additional
check before the build, to catch more problematic cases, but on the other hand
we have the error message anyway, though not so descriptive, and broken shader
code won't be used on gpu - so there are no lockups.

I doubt that non-LLVM shader backend will be able to handle that shader anytime
soon. LLVM backend currently can't handle it due to another problem, but it's
going to be fixed.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-05-26 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25  7:21 [Bug 50338] New: r600g: EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed ! bugzilla-daemon
2012-05-25  7:22 ` [Bug 50338] " bugzilla-daemon
2012-05-26  8:52 ` bugzilla-daemon
2012-05-26 10:11 ` bugzilla-daemon [this message]
2018-03-06 18:38 ` 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-50338-502-Luwu3iHDTQ@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