From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37476] [wine] Devil May Cry 4: TXD tgsi opcode unsupported / translation from TGSI failed / missing vertex shader
Date: Sun, 5 Jun 2011 22:32:34 -0700 (PDT) [thread overview]
Message-ID: <20110606053234.E4A0913004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-37476-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=37476
Mike Kaplinskiy <mike.kaplinskiy@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|Other |x86 (IA32)
AssignedTo|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
|.org |org
CC| |mike.kaplinskiy@gmail.com
--- Comment #1 from Mike Kaplinskiy <mike.kaplinskiy@gmail.com> 2011-06-05 22:32:34 PDT ---
[changing assignee as this is clearly a mesa bug]
piglit arb_shader_texture_lod-texgrad shows the problem (using
texture2DGradARB).
Currently running it may also get you a fortify crash due to TXD having 4
inputs (the max in the context structure is 3).
I'm attaching a patch that has an implementation. Unfortunately I can't seem to
get it to work entirely correctly. The piglit test looks almost correct but has
several artifacts in random places. If someone could point me in the right
direction (as I'm completely clueless), I would be happy to finish it. In case
it matters, piglit does not show any new failures from this patch.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-06-06 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 20:05 [Bug 37476] New: [wine] Devil May Cry 4: TXD tgsi opcode unsupported / translation from TGSI failed / missing vertex shader bugzilla-daemon
2011-06-06 5:32 ` bugzilla-daemon [this message]
2011-06-14 17:09 ` r600g TXD opcode (was: ... translation from TGSI failed / missing vertex shader) David Lamparter
2011-06-14 18:09 ` Sven Arvidsson
2011-06-15 7:22 ` Dave Airlie
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=20110606053234.E4A0913004E@annarchy.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).