Re: [Mesa3d-dev] Texutil optimizations - an interesting story

[Gareth H. <ga...@va...>]

Josh Vanderhoof wrote:
> 
> It looks like gcc is trying to keep the values as ubytes for too long.
> If you change r,g,b,a from GLubyte to GLuint, it seems to to a better
> job.

Yes, I had noticed a significant speedup by doing this.  The final
version of the templated code wasn't going to be this exact code.

However, I was more interested in the fact that gcc output vastly
different assembly depending on where the C code was located, with such
a huge difference in performance.  I though I might share this with the
list.

-- Gareth