News for hackers. Stuff that matters.
Re:How AMD Won, Then Lost by technofiend on Wednesday December 09, 2015 @09:46PM (#10708536)
I guess the real question is will AMD have a compiler to match Intel's when ZEN is released?
Re:How AMD Won, Then Lost by _delirium on Thursday December 10, 2015 @01:39AM (#10709220)
Afaict AMD is putting their compiler-engineering effort into trying to improve gcc performance on their chips, rather than starting a separate compiler project. They are a lot smaller than Intel, so I'm not sure they can spare the resources to build an AMD analog to Intel's icc.
Re:How AMD Won, Then Lost by Keyframe on Thursday December 10, 2015 @09:41AM (#10710772)
Didn't Intel's compiler start out from Intel buying Digital's compiler stuff?
Re:How AMD Won, Then Lost by mixmastamyk on Thursday December 10, 2015 @01:56AM (#10709269)
Who uses Intel's compiler? I was under the impression most were using Microsoft's, or gcc/clang perhaps.
Re:How AMD Won, Then Lost by lmm on Thursday December 10, 2015 @05:35AM (#10709939)
Number crunching workloads, or the narrow HPC niche in which it works on a workstation rather than a cluster but you still need maximum performance from it - some physicists, astronomers, and geneticists. It's a fairly small niche but they buy new CPUs more than other people.
Re:How AMD Won, Then Lost by x0x0 on Thursday December 10, 2015 @04:44AM (#10709775)
people who care about performance, particularly simd or numerics performance. gcc has gotten better recently, but it's still slower ime.
Re:How AMD Won, Then Lost by nly on Thursday December 10, 2015 @07:08AM (#10710220)
On the other hand, Intels compiler does really dumb things with vanilla application code and has never performed better for any code I've ever written.
Re:How AMD Won, Then Lost by x0x0 on Thursday December 10, 2015 @02:43PM (#10712890)
Yeah, ymmv.

All high-perf code simply has to be meticulously performance tested; there's no other way to know on modern processors what is fastest.

Re:How AMD Won, Then Lost by S_A_P on Wednesday December 09, 2015 @10:32PM (#10708696)
I'm surprised nobody's hacked the Intel compiler to compile for AMD chips. I'm sure it's for fear of litigation.
Re:How AMD Won, Then Lost by berkut on Thursday December 10, 2015 @01:56AM (#10709270)
You don't need to these days (since 2011) - there have been numerous benchmarks over the years showing ICC generate binaries that perform better than MSVC++ for AMD processors.
Re:How AMD Won, Then Lost by throwaway7767 on Thursday December 10, 2015 @06:31AM (#10710108)
Interesting. I guess they must have finally stopped intentionally crippling ICC for non-intel processors[0].

[0] http://www.agner.org/optimize/blog/read.php?i=49#49

Re:How AMD Won, Then Lost by andrewflnr on Wednesday December 09, 2015 @11:24PM (#10708881)
I don't think you would have to do that. Couldn't you write a tool that just patches out the "be stupid if this is an AMD chip" code from an intel-compiled binary?
Re:How AMD Won, Then Lost by TazeTSchnitzel on Thursday December 10, 2015 @07:33AM (#10710298)
Intel's compiler would check for the presence of a feature (SSE etc.) and also for "GenuineIntel". So you could simply remove the latter part and it should work fine, I think.
Re:How AMD Won, Then Lost by raverbashing on Thursday December 10, 2015 @05:07AM (#10709839)
Of course they did it, you just need to 'fix' the binary file, but there are several tools that do this