nv50: match VP outputs to FP inputs ourselves
authorChristoph Bumiller <e0425955@student.tuwien.ac.at>
Sun, 29 Nov 2009 12:33:16 +0000 (13:33 +0100)
committerChristoph Bumiller <e0425955@student.tuwien.ac.at>
Sun, 29 Nov 2009 12:41:47 +0000 (13:41 +0100)
commit7494b829052a87d7a8c56c68300a110b40e401e8
tree0b7c56e2c513fe8ccb2431a395d605802409bef2
parent3f471c7948425a9c8ae23a563e0e816954a7589a
nv50: match VP outputs to FP inputs ourselves

For each FP input, don't assume that the VP output will be
at the same position, but scan the semantics instead, then
put the correct output reg indices into VP_RESULT_MAP.

Position is still assumed to be the first output/input.

See 07fafc7c9346aa260829603bf3188596481e9e62, which renders
previous assumptions incorrect.
src/gallium/drivers/nv50/nv50_program.c
src/gallium/drivers/nv50/nv50_program.h