[sldev] [VWR] Vectorization on i386?

[Callum Lerwick]

On Mon, 2007-12-03 at 20:13 +0000, Tofu Linden wrote: 
> Callum Lerwick wrote:
> >> What testing?  I thought you said you couldn't get this enabled on i386?
> >> Which part of the problem are you failing to reproduce?
> > 
> > The viewer runs, and always has run on my Athlon T-bird just fine. And
> > I've run it on my dual PII 333 system. If it were leaking SSE code into
> > places it shouldn't, I would have run into it by now.
> 
> It must be a bad brain day for me, because I still don't understand;
> the viewer runs and has always run on the Athlon because SSE code isn't
> enabled on i386 builds by default (and we happen to prefer GCC 3.4 for
> now which doesn't leak SSE code), which I thought was the whole point
> of this thread.

You seem confused about what I mean when I say "enabled". The whole
point of this thread is the SSE code is *there*, its getting compiled
into the viewer. Compiling the SSE code is *not* disabled under gcc.
Only under MSVC. The comments in llv4math.h and
llviewerjointmesh_sse2.cpp indicate this is the intention. SSE is not
compiled at all on "Windows". Though this would be another case of
saying "Windows" when you really mean MSVC...

By "enabled" in this thread I mean enabling the SSE code at *runtime*.
That is the problem. Which is what I have fixed. I'm not sure what
you're meaning by "not enabled", if you're saying its "not enabled" as
in "not compiled in at all", you're wrong. :)

I'm compiling with Fedora 8's gcc 4.1.2, and I've never run in to any
SSE leakage problems.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.secondlife.com/pipermail/sldev/attachments/20071203/7635b355/attachment.pgp