[1/4] wined3d/context: Track the number of render targets in FBO entries.

[Henri Verbeet]

On 21 March 2011 21:56, Adam Martinson <amartinson at codeweavers.com> wrote:
>
> Cuts CPU time in context_apply_fbo_state() in half.
This is meaningless. Which applications, and how much time of the
total is spent in context_apply_fbo_state()? How does this translate
into concrete thing like frame time? More importantly, why does this
change come before the one for tracking FBO dirty state? Avoiding
redundant FBO entry comparisons completely is likely to have a much
more significant effect than making the comparisons themselves
slightly cheaper in very specific applications.