Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Lame compile with ICL 9 (Read 4919 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Lame compile with ICL 9

Hi,

did anyone here try (and succeed) to compile Lame with the latest ICL?

I can't get it to work, when I run the exe it gives me something like:
The instruction at "0x00416fb4" referenced memory at "0x4fe4b3f4". The memory could not be "read".

I turned off all optimizations, but the problem remained.
As soon as I used the MS compiler the lame.exe works flawlessly.

bye,
Michael

Lame compile with ICL 9

Reply #1
I just recompiled here using ICL9.0 with the same optimisations used with 4.5 and the .exe runs fine. (3.97alpha)

Lame compile with ICL 9

Reply #2
Quote
I just recompiled here using ICL9.0 with the same optimisations used with 4.5 and the .exe runs fine. (3.97alpha)
[{POST_SNAPBACK}][/a]


hey john33, do u know if the ICL 9 slows down code when it's run on an AMD CPU?
(something like [a href="http://www.amd.com/us-en/assets/content_type/DownloadableAssets/AMD-Intel_Full_Complaint.pdf]this[/url])

Lame compile with ICL 9

Reply #3
Quote
Quote
I just recompiled here using ICL9.0 with the same optimisations used with 4.5 and the .exe runs fine. (3.97alpha)
[{POST_SNAPBACK}][/a]


hey john33, do u know if the ICL 9 slows down code when it's run on an AMD CPU?
(something like [a href="http://www.amd.com/us-en/assets/content_type/DownloadableAssets/AMD-Intel_Full_Complaint.pdf]this[/url])
[a href="index.php?act=findpost&pid=321458"][{POST_SNAPBACK}][/a]

Hmmm, a somewhat horrifying if interesting contention. I don't know because I haven't tried but if it can be demonstrated to be the case I, for one, will cease using the Intel compilers immediately. I am also interested as I am about to move to an AMD Athlon64 platform.

Lame compile with ICL 9

Reply #4
Quote
I just recompiled here using ICL9.0 with the same optimisations used with 4.5 and the .exe runs fine. (3.97alpha)
[a href="index.php?act=findpost&pid=321448"][{POST_SNAPBACK}][/a]

Which source did you use? I got it from cvs yesterday.
Did you use the latest MS-Platform SDK?

I never had this problem before, very strange :/.

bye,
Michael

Lame compile with ICL 9

Reply #5
@katharsis
do you use Makefile.MSVC or the studio project files?

Lame compile with ICL 9

Reply #6
Quote
Which source did you use? I got it from cvs yesterday.
Did you use the latest MS-Platform SDK?

I never had this problem before, very strange :/.

bye,
Michael
[a href="index.php?act=findpost&pid=321479"][{POST_SNAPBACK}][/a]

Current 3.97alpha CVS. I compiled using the VC6 IDE with ICL4.5 and 9.0 integrated.

Lame compile with ICL 9

Reply #7
Quote
Quote
I just recompiled here using ICL9.0 with the same optimisations used with 4.5 and the .exe runs fine. (3.97alpha)
[{POST_SNAPBACK}][/a]


hey john33, do u know if the ICL 9 slows down code when it's run on an AMD CPU?
(something like [a href="http://www.amd.com/us-en/assets/content_type/DownloadableAssets/AMD-Intel_Full_Complaint.pdf]this[/url])
[{POST_SNAPBACK}][/a]

[a href="http://www.heise.de/ct/inhverz/search.shtml?T=64-Bit-Werkstatt&Suchen=suchen]http://www.heise.de/ct/inhverz/search.shtm...t&Suchen=suchen[/url]
It seems the intel compiler has some optimization switch for Prescott CPUs (mainly SSE3, plus some other optimizations). If no Prescott CPU is detected, the code does not run. In above article they used a patched compiler and saw some improvements for AMD CPUs. One benchmark test showed some 36 percent performance boost.

Lame compile with ICL 9

Reply #8
First I tried MSVC 6 and the dsw, when I only got crashes I switched to the makefile, didn't make a difference .

 

Lame compile with ICL 9

Reply #9
The switches used in the Intel compiler enable optimisations specifically for Intel CPU's, regardless of whether another CPU would be compatible. It's an "only guaranteed to work on" thing. The letters of the switches match the codenames for the respective CPU cores where the features used were introduced in, -xW(illamette), -xP(rescott), etc. I'm not sure how much of a case AMD has here, but the binaries produced are indeed remarkably "intelligent" when it comes to detecting CPU's.
Veni Vidi Vorbis.