Pipeline separation preview

Ivan Gyurdiev ivg231 at gmail.com
Sat Jul 5 15:51:53 CDT 2008

Stefan Dösinger wrote:
> Oops, forgot to attach the archive
I like it, especially these parts:

- Interface decoupling - Moves FFP replacement code to using the FFP 
state table interface, instead of touching the unrelated shader interface
- Code separation - Code unrelated to shaders is moved out of the shader 
interface as a result (0020, 0021, 0022, 0048, 0049)
- Code separation - NV shader code pushed out into its own file, like 
ARBFS, ATIFS, GLSL - 0054, 0057, 0058, 0059 (if statements gone)
- Increased modularity - breaks up single state table into multiple 
parts, which can be individually manipulated w/o performance impact
- Moves towards OOP approach - state table structure is wrapped by a 
"fragment_pipeline" object with method vtable (0048)

I think it's moving in the right direction. It's also important that 
you've tried this on the NV extension, since now you have two pipeline 
replacements to test if the framework is sufficient or not.


More information about the wine-devel mailing list