All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52957] [r200] piglit glean/vp1-LIT test 2 (degenerate case: 0 ^ 0 -> 1) test fails
Date: Mon, 30 Jul 2012 14:19:43 +0000	[thread overview]
Message-ID: <bug-52957-502-vmTSP5PR3C@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-52957-502@http.bugs.freedesktop.org/>

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

Roland Scheidegger <sroland@vmware.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Roland Scheidegger <sroland@vmware.com> 2012-07-30 14:19:43 UTC ---
This is due to differences in LIT opcode between DX and OGL. AFAIK the chip can
only do the DX version (there's no documentation for this part of the chip, but
r300 could only do this too). Hence to make this opcode work correctly,
complicated workarounds might be needed - given the chip limits (program length
etc.) these might do more wrong than good. So unless you find some real app
where this is a problem noone will bother - not that many programs can use
vertex programs on r200 anyway since often new render paths also would require
fragment program.

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

      reply	other threads:[~2012-07-30 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 10:01 [Bug 52957] New: [r200] piglit glean/vp1-LIT test 2 (degenerate case: 0 ^ 0 -> 1) test fails bugzilla-daemon
2012-07-30 14:19 ` bugzilla-daemon [this message]

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-52957-502-vmTSP5PR3C@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.