My Athlon XP 1700+ shows as a T-Bird with CPU-Z. S38 appears not to work on it.
Maybe it's an Athlon 4 Mobile? This one is often recognized as an Athlon XP but isn't capable of SSE and is in reality a modernized Athlon Thunderbird.
How about optimizing the C37 (=plain MMX) further, as the SSE-version (S39X) also? My trusty old Athlon Thunderbird (and probably a bunch of other processors out there also) would be very thankful, as it already is for the C37-version :D
How about optimizing the C37 (=plain MMX) further, as the SSE-version (S39X) also? My trusty old Athlon Thunderbird (and probably a bunch of other processors out there also) would be very thankful, as it already is for the C37-version :D
C40 will be the next. Is it ok?
But don't rely on big improvement. SSE is a very strong weapon.
Perhaps 3DNow! would be interesting. MMX doesn't play...
How about optimizing the C37 (=plain MMX) further, as the SSE-version (S39X) also? My trusty old Athlon Thunderbird (and probably a bunch of other processors out there also) would be very thankful, as it already is for the C37-version :D
C40 will be the next. Is it ok?
But don't rely on big improvement. SSE is a very strong weapon.
Perhaps 3DNow! would be interesting. MMX doesn't play...
Do you expect D40 or S40 to be faster, or is it too soon to say? (My Athlon XP supports both 3DNow! and SSE, but not SSE2...)
It isn't question. D40 will be much slower.
3DNow! handles just 16 numbers againts 32 numbers of SSE.
It means that I won't be able to do overlapping under 3DNow!
The goal of D40 is doing a faster code than C40 for older AMD processors.
RE: RE: AMD added SSE
)
Maybe it's an Athlon 4 Mobile? This one is often recognized as an Athlon XP but isn't capable of SSE and is in reality a modernized Athlon Thunderbird.
Aloha, Uli
RE: My Athlon XP 1700+
)
Did you mean 1600+?
How about optimizing the C37
)
How about optimizing the C37 (=plain MMX) further, as the SSE-version (S39X) also? My trusty old Athlon Thunderbird (and probably a bunch of other processors out there also) would be very thankful, as it already is for the C37-version :D
Aloha, Uli
RE: RE: My Athlon XP
)
No.
I run 4 systems:
Athlon 1333mhz
AMD XP 1600+
AMD XP 1700+
AMD XP 2600+
The 1600 and 2600 both are SSE capable, but the Athlon and 1700 are not.
Seti Classic Final Total: 11446 WU.
RE: How about optimizing
)
C40 will be the next. Is it ok?
But don't rely on big improvement. SSE is a very strong weapon.
Perhaps 3DNow! would be interesting. MMX doesn't play...
Future plans:
C40 (387 compatible) -> S40 (SSE compatible) -> S240 (SSE2 compatible)
RE: RE: How about
)
Both my non-SSE systems (Athlon and XP 1700) support 3DNow! so this would be great for me if it works!
Seti Classic Final Total: 11446 WU.
RE: RE: C40 (387
)
Well, then I should do an add-in.
C40 (387 compatible) -> D40 (3DNow! compatible) -> S40 (SSE compatible) -> S240 (SSE2 compatible)
I'm looking forward to trying out the new official application. Both will use the same algorithm. Which will be faster? Cxx vs. new official?
The Sxx codes use different method, it will be the next suggestion to Bruce.
... and the amazing sin/cos interpolator :-)
RE: Well, then I should do
)
My trusty ol'Athlon will totally go nuts then :D
Aloha, Uli
RE: RE: RE: C40 (387
)
Do you expect D40 or S40 to be faster, or is it too soon to say? (My Athlon XP supports both 3DNow! and SSE, but not SSE2...)
RE: Do you expect D40 or
)
It isn't question. D40 will be much slower.
3DNow! handles just 16 numbers againts 32 numbers of SSE.
It means that I won't be able to do overlapping under 3DNow!
The goal of D40 is doing a faster code than C40 for older AMD processors.
Edit: But a good news, I like 3DNow! :-)