Bug 29436 - [r300g] glean/glsl1-do-loop: Unknown texture opcode BGNLOOP
Summary: [r300g] glean/glsl1-do-loop: Unknown texture opcode BGNLOOP
Status: RESOLVED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/r300 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-07 09:26 UTC by Priit Laes (irc: plaes)
Modified: 2010-08-07 10:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
glxinfo.log (21.89 KB, text/plain)
2010-08-07 09:27 UTC, Priit Laes (irc: plaes)
Details

Description Priit Laes (irc: plaes) 2010-08-07 09:26:16 UTC
Kernel: 2.6.35+
Mesa: git master d64a119c28376d7ce069dcec044ff9af7f93ff9c

Results for glean/glsl1-do-loop with continue and break

Returncode: 0

Errors:
r300 FP: Compiler Error:
r300_fragprog_emit.c::emit_tex(): Unknown texture opcode BGNLOOP
Using a dummy shader instead.
If there's an 'unknown opcode' message, please file a bug report and attach this log.

Output:
----------------------------------------------------------------------
GLSL test 1: test basic Shading Language functionality.

glsl1: Running single test: do-loop with continue and break
FAILURE:
  Shader test: do-loop with continue and break
  Expected color: 0.5, 0.5, 0.5, 0.5
  Observed color: 0, 0, 0, 1
glsl1:  FAIL rgba8, db, z24, s8, win+pmap, id 33
	0 tests passed, 1 tests failed.
Comment 1 Priit Laes (irc: plaes) 2010-08-07 09:27:19 UTC
Created attachment 37670 [details]
glxinfo.log

OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on RV370
OpenGL version string: 2.1 Mesa 7.9-devel
OpenGL shading language version string: 1.20
Comment 2 Tom Stellard 2010-08-07 10:03:35 UTC
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.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.