Summary: | rv670 + llvm = errors. | ||
---|---|---|---|
Product: | Mesa | Reporter: | Andy Furniss <adf.lists> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
R600_DUMP_SHADERS=2 ./gears &>gears-dump
Possible Fix |
Description
Andy Furniss
2012-12-22 23:46:55 UTC
Since mesa commit - 022122ee63b8a00afc23eaa347df934a79fb1d4c r600g: use tables with ISA info v3 I can run demos without flooding errors, but most of them don't render anything. The ones that do render something resemble what they should look like are all flawed/distorted eg, "textures" is almost normal but the actual textures are repeated rather than scaled to fit the surfaces. Can you run one of the demos and post the output with the environment variable R600_DUMP_SHADERS=2 Created attachment 74051 [details]
R600_DUMP_SHADERS=2 ./gears &>gears-dump
R600_DUMP_SHADERS=2 ./gears which doesn't render anything, but appears to be running OK eg. outputting sane fps stats and quitting normally with Esc.
Created attachment 74053 [details]
Possible Fix
It looks like we were telling the backend that RV670 is an R700 GPU, when it is really an R600. R600 chips uses a slightly different instruction encoding. This patch should fix it, can you test?
(In reply to comment #4) > Created attachment 74053 [details] > Possible Fix > > It looks like we were telling the backend that RV670 is an R700 GPU, when it > is really an R600. R600 chips uses a slightly different instruction > encoding. This patch should fix it, can you test? Yes, this fixes it - demos are all OK (well at least the same as my rv790) and a brief run of etqw worked. Fixed by commit 257006e2a4201c11ca5f800a74ac4aaf62a7bfc1 |
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.