Core 2 SSE4 version spied

[FloridaBear]

Well, I think the cat will soon be out of the bag, so I thought I'd pass along the stderr from a result I found:

Optimized Windows SETI@Home Enhanced application
Version info: Windows SSE4-Core 2 32-bit V5.15 'Chicken Good!' (R-1.41|+more_vec|xT)
Compiled by Simon Zadra (KWSN - Chicken of Angnor) - Member of the Knights who say Ni! (http://www.kwsn.net)
Download Updates at: http://www.zadra.org/seti_enhanced/

By the way, this is the fastest Core2 Duo out there at the moment...
http://setiathome.berkeley.edu/show_host_detail.php?hostid=1358316

It's running at 3.3GHz and doing 62 credit WUs in 4000 seconds. That's pretty quick.

So, Simon...are we getting near a "general" release of that particular client?

[UPDATE]
It looks like this host has been running the SSE4 Core 2 client since October 13, and there were no validation errors except the first WU. Seems like it's ready for prime time to me!

[Adrenalin2]

What a MONSTER! 

[Vyper]

Hmm i guess who's machine is that . 

[Simon]

Er,

lol. Initial testing with that app didn't show any improvement, but people have been telling me it kicks butt on Core 2 systems. Guess I'll have to dig it up again

That is a pretty old compile, by the way, nothing based off of new code. The only thing that's different are some IPP-related extra includes and defines in analyzeFuncs.cpp.
Seems to have worked better than I expected

I'll have to do some benches on the Woodcrest server to see what's what, will let you know.

Regards,
Simon.

[FloridaBear]

Ah, ok. Still, that machine has a higher RAC than a faster Conroe, so maybe there is merit... thanks for the reply, Simon.

[Darkclown]

Er,

lol. Initial testing with that app didn't show any improvement, but people have been telling me it kicks butt on Core 2 systems. Guess I'll have to dig it up again

That is a pretty old compile, by the way, nothing based off of new code. The only thing that's different are some IPP-related extra includes and defines in analyzeFuncs.cpp.
Seems to have worked better than I expected

I'll have to do some benches on the Woodcrest server to see what's what, will let you know.

Regards,
Simon.

I've got a Core 2 sitting here which I'd throw into testing if you want

[Simon]

Well folks,

I've just put the 1.41 Core 2 SSSE3-optimized app online.

So test and run to your heart's content

Happy crunching,
Simon.

[Dirk Sadowski]

Well folks,
I've just put the 1.41 Core 2 SSSE3-optimized app online.
So test and run to your heart's content
Happy crunching,
Simon.

Hello Simon!

This app will run on an Intel(R) Core(TM) 2 Duo (Mobile) T7200, too?

Because on the S@H- Board you said: "This app has been tested on Conroe and Woodcrest systems..."
...and the T7200 is a Merom...


Greetings!


How is the state of the 64Bit apps (Windows and Linux) ?   


BTW. SSSE3 is the improvement of SSE3? I thought it'll called SSE4?

[Simon]

Well, I thought it was SSE4 too, but Intel told us it wasn't. Core 2 systems do SSSE3 (Supplemental SSE3), not SSE4.

It should run fine on a Merom, but to my knowledge was not tested on one yet.

HTH,
Simon.

[FloridaBear]

Thanks, Simon. C2 version installed and running...I will post back in a few days with results.

[BORG]

Simon.

To compile then the use is use_ssse3? or use_sse4?

zcpu reports it as sse4

Borg

[Simon]

CPU-Z is incorrect about it, but will probably soon be updated.
The USE flag is USE_SSE4 though, because I haven't edited it yet

Regards,
Simon.

[Josef W. Segur]

CPU-Z is incorrect about it, but will probably soon be updated.
The USE flag is USE_SSE4 though, because I haven't edited it yet

Regards,
Simon.

CPU-Z history shows:

1.37 - October 2006
- Intel Core 2 Quad, Celeron 360, Mobile Core 2 Duo T5200 support.
- Changed SSE4 to SSSE3 (Supplemental SSE3).
- Added VIA VT8237A southbridge.
- New HTML report.
- Several bug fixes.

                                                                           Joe

[BORG]

Thanks simon

So when using your source code 1.41 core 2 - The use is use_sse4 till further notice.

Thanks again. 

Any update on the 64 bit front?