Home  |  News  |  Reviews  | About Search :  HardWare.fr 



MiscellaneousStorageGraphics CardsMotherboardsProcessors
Advertise on BeHardware.com

News of the day

  • GeForce 300Ms, NVIDIA renames again!
  • 1st tests of the Vertex 2 / SandForce SSD
  • VIA launches USB 3.0
  • News of the FTC case and Intel compilers
  • Is EVGA relaunching Skultraill?
  • The Radeon Mobility 5xxxs are on their way
  • Core i3/i5, also on laptops!
  • Archives

    Janvier 2010
    LMMJVSD
    1 2 3
    4 5 6 7 8 9 10
    11 12 13 14 15 16 17
    18 19 20 21 22 23 24
    25 26 27 28 29 30 31

    You can read previous news using our archives.

    << Previous day's news
    December 24, 2009
    Next day of news >>
    January 5, 2010



     News of the FTC case and Intel compilers
      Posted on 04/01/2010 at 14:44 by Marc
    Imprimer cette news Envoyer cette news par e-mail

    The FTC’s proceedings against Intel in December were important for a number of reasons. Among them, the part concerning compilers is the least known by the general public.

    In addition to processors, Intel also sells a range of compilers. They have a reputation for high performance and are also generally faster with Intel processors, so much so that they're sometimes preferred to compilers from third parties (Gnu, Microsoft) by those who prioritise rapidity above all else.

    Like all other compilers, the Intel ones offer various compilation options. You can therefore target specific levels of instruction (LA32, SSE, SSE2, SSE3, etc.) but a more elegant option allows you to generate executables that integrate different code that is executed according to the processor’s features.

    And here lies the rub. With this option on the Intel compilers, the executable will first check to see if the processor is an Intel one before executing the optimal code for the features of that particular processor. When it isn't an Intel processor, the default code is used whatever the instruction set supported by the CPU!

    Today the default code is SSE/SSE2 code, but a few years ago it was non-vector code (pure x86) that was therefore executed on the Athlon 64s! The current situation is less problematic than it was in the past then but still, a programme compiled with this option won’t, for example, execute SSE3 code on a Phenom II.

    Of course, there are alternatives, the first of course being not to use Intel compilers. Where this isn’t possible, you can compile your exectuable in several versions and have a programme that launches the right version upstream. Better still, you can replace the Intel CPU with another that works whatever the CPU manufacturer (page 125 onwards of this document) !

    As part of its enquiry into Intel’s practices, the FTC, alerted to the issue, has come out against Intel compilers as uncompetitive behaviour, qualifying the compiler itself as defective ("defective compiler", page 21 of this document). As a result it has requested that Intel put a compiler from which this code is excluded at the disposition of developers and take responsibility for any recompilation of programmes compiled with the “defective” versions.

    Of course, if the FTC’s request was seen through, it wouldn’t transform an Athlon II into a Core i7, but in terms of programmes compiled with Intel software, there could be a gain on rival CPUs, which is still a bonus.


    << Previous day's news
    December 24, 2009
    Next day of news >>
    January 5, 2010


    Copyright © 1997- Hardware.fr SARL. All rights reserved.
    Read our privacy guidelines.