Let's nt forget, that Intel Compiler is above all a vector compiler. Comapred to say gcc with full P4 optimizations it will still offer substantialy better results (ofcurse only in situations witch benefit from vectorization).
Printable View
Let's nt forget, that Intel Compiler is above all a vector compiler. Comapred to say gcc with full P4 optimizations it will still offer substantialy better results (ofcurse only in situations witch benefit from vectorization).
I used both intel EMT64 compiler v8.1 and gcc on A64 3500+ with SuSe Linux 9.1, surprisingly, the intel binary was twice the size of gcc own. Intel compiled binary also run twice slower even with a highly vectorized code.
Anyway, I just found this(Intel compiler patch for AMD A64) a while ago, I hope Intel is not shooting herself in the leg. http://www.theinquirer.net/?article=22750
:confused: Anyone tried it so far? Results?
:toast:
anyone tried???? it would be great if it gives me 22% speed up in super pi
Hi All
I've downloaded the source code to this program and compiled it. I'm currently running through loads of EXEs to see which ones can be patched and which can't.
So far, the ones you may or may not be interested.
Super Pi - No Patch
PiFast 4.3 - No Patch
3DMark2001SE - PATCH! :D I wonder what difference it makes. Rendered Useless
3DMark2003 - No Patch
3DMark2005 - Patch, Rendered Useless
PCMark2004 - Patch, Rendered Useless
FarCry.exe - No Patch
Editor for Farcry - PATCH
HL2 - No patch
United Devices, ALL the EXEs - No Patch
WINRAR, WinRAR.exe, Unrar.exe and RAR.exe - ALL can be patched! Hoping for faster file archiving now :D Works good so far, dunno if it's any faster though.
Prime 95 - No Patch
Speedfan - Patch - Rendered Useless
WMPLAYER.EXE - No Patch
Explorer.exe(Win XP x64) - No Patch
MPLAYER2.exe - No Patch
Lame.exe - Patch, Rendered Useless
SANDRA 2005 - No Patch
I'll post more as I know more.
I've attached the program to this post as well so you can try it for yourself! As usual, I accept no responsibility for any damage it may cause when you use it!
Anyone else??
so can someone tell me what to do with this??? does it work with normal winxp pro? how much benifits i looking at?
If this works it ruins everything and make the whole scene a mess ?
It's not a hack saaya (at least not in the illegal or reverse engineering sense), it merely disables a check for an Intel processor in cases where SSE and SSE2 compatibility are issues. Programs that make heavy use of SSE/SSE2 and do NOT check for these feature flags but merely check for the correct Intel processor, stand to see large improvements in performance.
Had the processor check been written correctly, these programs would already be running at full steam. ;)
And yes, unfortunately the A64 does not handle packed/vectorized SSE2 with greater efficiency than scalar :doh:
great, i hope this works amd 22% faster for free :) well on the apps that use the optimization
I think things based on the Quake 3 engine do this. Probably the UT engine too. I know that I usually need to manaully force SSE to on when I play games using those engines. Maybe if you find a game where it doesn't allow you to force flags it would help alot.Quote:
Originally Posted by matt9669
quake 3 performs flag checks, and I assume Unreal does too.. its quite bad form not to, really.
ummm....... so anybody help me out, what to do with this proggy?
You need to run in it in command prompt.
"iccout filename.exe"
It will say "Subtituting Code" if it actually finds the Intel only instruction, it replaces it with a NOP(No operation).
Just beware, from my testing so far, it renders a lot of programs useless, i.e. the Intel only instruction is in there for a reason!
EDIT: Just tested WinRAR file compression. It's actually slower(About 5%) with the patched version. This suggests to me that some software may be using this Intel only check to determine which codepath to use. This also explains why some software becomes useless after the patch.
I'm no expert, but dont AMD and Intel BOTH support SSE/SSE2 (in P4 and Athlon64), and SSE3 in Venice/Prescott. What "Intel-only" instructions could there be, other than the 4-5 that are reserved for Intel Hyperthreading... I ask you since you seem to be on the ball with this stuff..Quote:
Originally Posted by Walrusbonzo
I'm not really that much on the ball, I just read the article and understood it.Quote:
Originally Posted by ***Deimos***
Took the source code, compiled it and started to play with it :)
This is only for programs that have been compiled with the Intel optimising compiler, and only with Intel specific optimisations turned on. Plus this is from over a year ago, there surely have been revisions to their compiler, probably rendering this program useless. There is little point of trying this thing out, it'll probably just corrupt your programs. Also, if the programs do checksums on themselves, they'll be rendered useless, as this modifies the exe.
HOLY THREAD RESURRECTION BATMAN! :eek: :lol:
well they (intel) called it hack :D i thougt its funny haha i agree its not really hacked, at least i wouldnt call it that... but i think officially it is hacked, no? they mean hacked as to manipulated without approval of the owner.Quote:
Originally Posted by matt9669
you can also call it patched :D
and yeah, the a64 is bad with sse and sse2, BUT sse and sse2 are more universal... so if the programs have unefficient code sse and sse2 might still be faster on the a64, no?
its mostly about compability though so apps that use sse2 can work alright on a64s i guess. the latest compiler story is hilarious! :lol:
intel will have to update their won compiler to work with a64s :rofl:
and saaya, please post in the right section next time! this surely doent belong in the xoc section! :slapass:
:D
actually they are pretty good with sse2, thats why sse3 (re-organized sse2) doesnt give much of a boost.