From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29436] [r300g] glean/glsl1-do-loop: Unknown texture opcode BGNLOOP
Date: Sat, 7 Aug 2010 10:03:35 -0700 (PDT) [thread overview]
Message-ID: <20100807170335.7D6E41300AC@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29436-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=29436
Tom Stellard <tstellar@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #2 from Tom Stellard <tstellar@gmail.com> 2010-08-07 10:03:35 PDT ---
Sorry, your hardware can't do fragment shader loops. We try to emulate loops
the best we can on the r300 cards, but we can't really handle break and
continue statements.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2010-08-07 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 16:26 [Bug 29436] New: [r300g] glean/glsl1-do-loop: Unknown texture opcode BGNLOOP bugzilla-daemon
2010-08-07 16:27 ` [Bug 29436] " bugzilla-daemon
2010-08-07 17:03 ` 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=20100807170335.7D6E41300AC@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