Bug 50325 - Glyphy bad render on r600g (software render is fine) - too many registers?
Summary: Glyphy bad render on r600g (software render is fine) - too many registers?
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 8.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-24 14:56 UTC by Török Edwin
Modified: 2018-03-06 18:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
apitrace (cf. https://github.com/apitrace/apitrace/tree/1.0) (145.52 KB, application/octet-stream)
2012-05-24 14:56 UTC, Török Edwin
Details
r600g-bad.png (13.65 KB, image/png)
2012-05-24 14:57 UTC, Török Edwin
Details
sw-good.png (166.30 KB, image/png)
2012-05-24 14:57 UTC, Török Edwin
Details

Description Török Edwin 2012-05-24 14:56:46 UTC
Created attachment 62078 [details]
apitrace (cf. https://github.com/apitrace/apitrace/tree/1.0)

I just tried Glyphy on r600g and the output is very bad.
Don't know if its Glyphy bug or Mesa bug, but if I force software rendering in Mesa then I do see the output.

Attached screenshots of bad (r600g) and good (software render).

The bad render was obtained by:
demo/glyphy-demo

The good one:
LIBGL_ALWAYS_SOFTWARE=1 demo/glyphy-demo

I tested on:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL version string: 2.1 Mesa 8.0.2
OpenGL shading language version string: 1.20

I'll try to test on mesa git later to see if its still an issue there.

Also attached is a an apitrace, and the bad render can be reproduced with:
build/glretrace lt-glyphy-demo.trace

The good render (initialization a bit slow, but works):
LIBGL_ALWAYS_SOFTWARE=1 build/glretrace lt-glyphy-demo.trace

The source code for Glyphy can be found here:
https://code.google.com/p/glyphy/source/checkout
Comment 1 Török Edwin 2012-05-24 14:57:08 UTC
Created attachment 62079 [details]
r600g-bad.png
Comment 2 Török Edwin 2012-05-24 14:57:24 UTC
Created attachment 62080 [details]
sw-good.png
Comment 3 Török Edwin 2012-05-25 00:22:27 UTC
With the git version of Mesa I get an error, opened new bug here: https://bugs.freedesktop.org/show_bug.cgi?id=50338
EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed !
Comment 4 Török Edwin 2012-05-26 01:52:53 UTC
(In reply to comment #3)
> With the git version of Mesa I get an error, opened new bug here:
> https://bugs.freedesktop.org/show_bug.cgi?id=50338
> EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed !

The bad render might be because the shader tries to use too many registers, some earlier version of Mesa git printed some errors about GPR count limit being exceeded.
Comment 5 cyberkm 2016-06-24 12:56:04 UTC
Bump
Comment 6 Vedran Miletić 2016-06-24 15:42:51 UTC
(In reply to cyberkm from comment #5)
> Bump

Have you confirmed it happens with latest Mesa git? What hardware did you try it on?
Comment 7 cyberkm 2016-07-01 13:31:15 UTC
Yep, latest mesa git.

05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Antilles [Radeon HD 6990]

mesa r600 gallium.

The app works fine if i switch to software renderer.
Comment 8 Gert Wollny 2017-10-08 16:11:31 UTC
Could you re-test with the latest mesa-git? As of mid September some patches landed that improved the register use. 

I myself tried it on an AMD 6850 HD and the trace works fine now.
Comment 9 Gert Wollny 2018-03-06 18:33:59 UTC
This should be fixed since version 17.2.
Comment 10 Gert Wollny 2018-03-06 18:41:26 UTC
Actually, that should be v17.3.


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.