On 04/13/2010 08:07 AM, Luca Barbieri wrote: > On nv30/nv40 support for patching fragment programs is already > necessary (constants must be patched in as immediates), and this can > be handled by just patching the end of the fragment program to include > a variable number of instructions to copy a temp to COLOR[x]. > > It's possible that there could be a hardware mechanism too, haven't checked. > > If other MRT-capable hardware already has this kind of fragment > program patching or supports this in hardware, then a new TGSI > semantic or register file can be added for this, and drivers can > easily implement that without recompilation. > nv50 passes, we check if multiple color results are written and if not, we don't set the FP_CTRL_MULTIPLE_RESULTS bit, and COLOR[0] goes to all RTs :-) I think nv40 might have that too, check the bits in your FP_CONTROL.
> Drivers could also just unconditionally write all color outputs as a > first implementation or if that doesn't affect performance. > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Mesa3d-dev mailing list > Mesa3d-dev@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mesa3d-dev ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
