<html>
<body>
<blockquote type=cite class=cite cite="">On Mon, Jan 4, 2010 at 2:34 PM,
Matt Olander
<<a href="mailto:matt@ixsystems.com">matt@ixsystems.com</a>>
wrote:<br>
<dl>
<dd>On Mon, Jan 4, 2010 at 12:28 PM, Arthur Koziol
<<a href="mailto:A-Koziol@neiu.edu">A-Koziol@neiu.edu</a>>
wrote:<br>
<dd>> On 01/04/2010 12:58 PM, Matt Olander wrote:<br>
<dd>>><br>
<dd>>> On Mon, Jan 4, 2010 at 10:34 AM,
<a href="mailto:doverosx@gmail.com">doverosx@gmail.com</a>
<<a href="mailto:doverosx@gmail.com">doverosx@gmail.com</a>><br>
<dd>>> wrote:<br>
<dd>>><br>
<dd>>>><br>
<dd>>>> Arthur Koziol wrote:<br>
<dd>>>><br>
<dd>>>>><br>
<dd>>>>><br>
<dd>>>>>
<a href="http://www.osnews.com/story/22683/Intel_Forced_to_Remove_Cripple_AMD_Function_from_Compiler_">
http://www.osnews.com/story/22683/Intel_Forced_to_Remove_Cripple_AMD_Function_from_Compiler_</a>
<br>
<dd>>>>><br>
<dd>>>>> Pretty evil if you asked me. Seems Intel is batting
a thousand lately.<br>
<dd>>>>> Hope AMD takes 'em to the cleaners.<br>
<dd>>>>> _______________________________________________<br>
<dd>>>>> Testing mailing list<br>
<dd>>>>>
<a href="mailto:Testing@lists.pcbsd.org">Testing@lists.pcbsd.org</a><br>
<dd>>>>>
<a href="http://lists.pcbsd.org/mailman/listinfo/testing" eudora="autourl">
http://lists.pcbsd.org/mailman/listinfo/testing</a><br>
<dd>>>>><br>
<dd>>>>><br>
<dd>>>>><br>
<dd>>>><br>
<dd>>>> Interesting...I thought it was a fact that WAS widely
known and the<br>
<dd>>>> issue remedied by the order of the FTC in 2000-2001?
Circa K7 Athlons.<br>
<dd>>>><br>
<dd>>>> Intel seems to be quite evil in how they handle some key
operations, of<br>
<dd>>>> course, the way they have been "handling"
business these days has earned<br>
<dd>>>> their appearance in an OpenBSD song ;).<br>
<dd>>>><br>
<dd>>><br>
<dd>>> It *is* the Intel Compiler, after all. Nobody has to use it
and I'm<br>
<dd>>> not really sure why anybody would try to use it on a
non-Intel system<br>
<dd>>> ;)<br>
<dd>>><br>
<dd>>> -matt<br>
<dd>>><br>
<dd>><br>
<dd>> Matt,<br>
<dd>><br>
<dd>> Bigger picture than just "use something else", imagine
all the lost revenue<br>
<dd>> for AMD because something showed better benchmarks with Intel
versus AMD and<br>
<dd>> someone went with Intel as a result. Evil is as evil does. It's
funny though<br>
<dd>> that when you look at the TOP500, top 3 spots run AMD.
HA!<br><br>
<dd>Haha, good point, Arthur. It's definitely a shady thing to do on<br>
<dd>Intel's part but I'm just not surprised to find that an Intel
Compiler<br>
<dd>would compile more efficiently on Intel CPU's. I can't imagine a
large<br>
<dd>AMD cluster compiling their custom code on anything closed and<br>
<dd>Intel-specific like the Intel Compiler though. Ironically, we're<br>
<dd>trying to get some traction with Intel to get a modern port of
the<br>
<dd>compiler on FreeBSD, along with some development tools that are<br>
<dd>currently Windows and Linux specific.<br><br>
<dd>While AMD may have caught Intel with their pants down a few years
ago<br>
<dd>and had the edge, there is no doubt that the tide has turned and
Intel<br>
<dd>responded with very fast modern CPUs, regardless of what the code
is<br>
<dd>compiled on. I'm sure we'll see AMD step it up in their next<br>
<dd>architecture :)<br>
<font color="#888888"><br>
<dd>-matt<br>
</font>
<dd>_______________________________________________<br>
<dd>Testing mailing list<br>
<dd><a href="mailto:Testing@lists.pcbsd.org">Testing@lists.pcbsd.org</a>
<br>
<dd>
<a href="http://lists.pcbsd.org/mailman/listinfo/testing" eudora="autourl">
http://lists.pcbsd.org/mailman/listinfo/testing</a><br><br>
</dl><br>
I've been experimenting a bit with clang and llvm on FreeBSD/PC-BSD and
Debian lately. I haven't tried doing any performance testing with the
compiled executables against the Intel compiler, but it does compare
favorably with gcc. Really close in execution time, but compiles FAR
faster.</blockquote><br>
CLANG, that's the one I was trying to think of. All those riding the GCC
sucks bus are fawning over it to take over as the default
compiler.<br><br>
Arthur</body>
</html>