Summary: | Glyphy bad render on r600g (software render is fine) - too many registers? | ||
---|---|---|---|
Product: | Mesa | Reporter: | Török Edwin <edwin+bugs> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | freedesktop |
Version: | 8.0 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
apitrace (cf. https://github.com/apitrace/apitrace/tree/1.0)
r600g-bad.png sw-good.png |
Description
Török Edwin
2012-05-24 14:56:46 UTC
Created attachment 62079 [details]
r600g-bad.png
Created attachment 62080 [details]
sw-good.png
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 ! (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. Bump (In reply to cyberkm from comment #5) > Bump Have you confirmed it happens with latest Mesa git? What hardware did you try it on? 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. 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. This should be fixed since version 17.2. 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.