News for hackers. Stuff that matters.
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