Whether or not the current page has anything to do with compilers.
Also, judging by the URL they made it an 'article' instead of a 'page' again... I'll have to see if I can get someone to fix that.
Is it just me or does that not actually fix the problem?
I don't agree either, but it's a perfectly valid solution (and probably the best for Intel's bottom line).
They should have originally used supported flags for different features instead of blacklisting the name, but it's still difficult to know what chips support what and whether it's worth using those features, due to different instruction latency, etc.
ICC get register dynamic code switching to different paths in the exe, so that if the chip supports AVX2, it'll use that code path.
they are not worried about fines. fines are cheap for those companies. they are worried about market control.
they are what they are thanks to phoenix reverse engineering IBM bios and the rise of the generic PC market. Now they fear anyone that can enter the market as easily as they entered and hope to not make the same mistake IBM did.
Since then Intel settled the lawsuit by paying $10M and agreeing to add the following disclaimer to their compilers: "Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors..." http://software.intel.com/en-us/articles/optimization-notice... http://www.anandtech.com/show/3839/intel-settles-with-the-ft...