[sldev] SSE2 / Ouch

[Dirk Moerenhout]

Well apparently in this case the goal is also to test, on the run,
whether SSE is really faster. In that way CPU's with lousy SSE can
still revert to a faster simple version. So even for SSE CPU's we need
the non-SSE code.

Off course splitting the binaries is easiest once we start to have
many CPU specific optimisations. But I had the impression during a
previous discussion that this was not wanted.

Given the size of an exe and how big a bootstrap exe would be I think
it would actually be not such a bad idea to distribute a single
download that detects CPU and starts the correct client. Or off course
an installer that downloads the correct version from the net.

Dirk aka Blakar Ogre

> Would it be easier rather than making complex auto detection code, to
> simply distribute two versions with and without SSE enabled? It should
> be trival to batch build different versions in visual studio with
> different build options. May be if we want to be clever the/an
> installer can detect the SSE capability and then download the correct
> file.
>
> --
> Robin Cornelius
> http://www.byteme.org.uk
>