History log of /external/mesa3d/src/gallium/drivers/radeon/AMDGPUSubtarget.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
2f921101c0826dc52a2c69f85c3da0f7f6e8212a 30-Jul-2012 Tom Stellard <thomas.stellard@amd.com> radeon/llvm: Rename all AMDIL* classes to AMDGPU*
/external/mesa3d/src/gallium/drivers/radeon/AMDGPUSubtarget.h
b72ab79d73b29ec087d90cf2c698adbab4db5def 30-Jul-2012 Tom Stellard <thomas.stellard@amd.com> radeon/llvm: Merge AMDILSubtarget into AMDGPUSubtarget
/external/mesa3d/src/gallium/drivers/radeon/AMDGPUSubtarget.h
9c42fb6f26bb7db1bc793f5fcc922bbae6700d74 27-Jul-2012 Tom Stellard <thomas.stellard@amd.com> radeon/llvm: Change the tablegen target from AMDIL to AMDGPU
/external/mesa3d/src/gallium/drivers/radeon/AMDGPUSubtarget.h
cd287301ec598d2811f3f85c03d23bae01be2359 20-Jun-2012 Tom Stellard <thomas.stellard@amd.com> radeon/llvm: Use the VLIW Scheduler for R600->NI

It's not optimal, but it's better than the register pressure scheduler
that was previously being used. The VLIW scheduler currently ignores
all the complicated instruction groups restrictions and just tries to
fill the instruction groups with as many instructions as possible.
Though, it does know enough not to put two trans only instructions in
the same group.

We are able to ignore the instruction group restrictions in the LLVM
backend, because the finalizer in r600_asm.c will fix any illegal
instruction groups the backend generates.

Enabling the VLIW scheduler improved the run time for a sha1 compute
shader by about 50%. I'm not sure what the impact will be for graphics
shaders. I tested Lightsmark with the VLIW scheduler enabled and the
framerate was about the same, but it might help apps that use really
big shaders.
/external/mesa3d/src/gallium/drivers/radeon/AMDGPUSubtarget.h