[sldev] SSE/Vector stuff

Dzonatas dzonatas at dzonux.net
Sun Jul 8 11:52:07 PDT 2007


The reason you really don't want to patch the source files is for 
portability and that there may be more _vec, _sse, and _sse2 type files 
for other optimizations. Really, it is that portion of the filename, the 
"_vec", "_sse", and "_sse2" that determines what compiler options should 
be on and what headers should not be included. Those particular 
implementations can not be mixed with pre-compiled headers, for example.

If you look in the SConstruct, you'll see it specifically checking for 
the filenames in order to determine to turn on the optimizations.

I used VS2005 Express with a version of the SConstruct files that 
compiles with VS2005, which makes all these little options on each file 
very transparent. Obviously, I could not change the VS2003 project files 
with VS2005.

As for VBOs, not everybody leaves them on. If you are thinking of trying 
to align that data, it has been tried. There is a bug LL's gl indices 
implementation that didn't allow align data, even though gl supports it. 
I still have the patch for the VBO alignment if you want to figure it out.

Nicholaz Beresford wrote:
>
> Dirk,
> Dzon,
>
> thanks for the info.  I'll probably opt for a
> source change in those to files, because it is
> easier to patch them again for later releases,
> but now at least I know what I have to look for.
>
> Is this change intended long term for something
> else?  I mean, most people are probably running
> with VBO's right?

-- 
Power to Change the Void


More information about the SLDev mailing list