summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorNicolai Haehnle <nhaehnle@gmail.com>2016-06-07 21:37:17 +0000
committerNicolai Haehnle <nhaehnle@gmail.com>2016-06-07 21:37:17 +0000
commitc00e03b8f57c6ba9dad2d9ae33d78a9b81c9cc5e (patch)
treed6c2219a60b6df16c8d04cfc605a67d46548e3da /lldb/packages/Python/lldbsuite/test/python_api
parentf0f62d8451da35c2557e1385bac160b93b005b89 (diff)
downloadbcm5719-llvm-c00e03b8f57c6ba9dad2d9ae33d78a9b81c9cc5e.tar.gz
bcm5719-llvm-c00e03b8f57c6ba9dad2d9ae33d78a9b81c9cc5e.zip
AMDGPU: Add amdgpu-ps-wqm-outputs function attributes
Summary: The presence of this attribute indicates that VGPR outputs should be computed in whole quad mode. This will be used by Mesa for prolog pixel shaders, so that derivatives can be taken of shader inputs computed by the prolog, fixing a bug. The generated code could certainly be improved: if a prolog pixel shader is used (which isn't common in modern OpenGL - they're used for gl_Color, polygon stipples, and forcing per-sample interpolation), Mesa will use this attribute unconditionally, because it has to be conservative. So WQM may be used in the prolog when it isn't really needed, and furthermore a silly back-and-forth switch is likely to happen at the boundary between prolog and main shader parts. Fixing this is a bit involved: we'd first have to add a mechanism by which LLVM writes the WQM-related input requirements to the main shader part binary, and then Mesa specializes the prolog part accordingly. At that point, we may as well just compile a monolithic shader... Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95130 Reviewers: arsenm, tstellarAMD, mareko Subscribers: arsenm, llvm-commits, kzhuravl Differential Revision: http://reviews.llvm.org/D20839 llvm-svn: 272063
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud