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 31800] [r300g] src/mesa/state_tracker/st_mesa_to_tgsi.c:228:src_register: Assertion `index >= 0' failed.
Date: Sun, 21 Nov 2010 13:38:21 -0800 (PST)	[thread overview]
Message-ID: <20101121213821.9662113004D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31800-502@http.bugs.freedesktop.org/>

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

Marek Olšák <maraeo@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Drivers/Gallium/r300        |Mesa core
         AssignedTo|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
                   |.org                        |org

--- Comment #1 from Marek Olšák <maraeo@gmail.com> 2010-11-21 13:38:20 PST ---
glsl-fs-uniform-array-6 surpasses hardware limits of r300 (it uses 1024 vec4s,
while only 256 are supported).

To "fix" this for r300, the test should check for
GL_MAX_FRAGMENT_UNIFORM_COMPONENTS_ARB and skip accordingly (there's a patch in
ML which sets MaxUniformComponents in st/mesa).

I am reassigning this bug to Mesa core, because the assertion failure is
outside the driver.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2010-11-21 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21  2:31 [Bug 31800] New: [r300g] src/mesa/state_tracker/st_mesa_to_tgsi.c:228:src_register: Assertion `index >= 0' failed bugzilla-daemon
2010-11-21 21:38 ` 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=20101121213821.9662113004D@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