Changes between Version 24 and Version 25 of CompilingCloudyC10


Ignore:
Timestamp:
2012-10-25T10:44:48Z (5 years ago)
Author:
peter
Comment:

add support for icc 13.0

Legend:

Unmodified
Added
Removed
Modified
  • CompilingCloudyC10

    v24 v25  
    108108== Intel icc ==
    109109
    110 We tested versions 10.x, and 11.x of icc. The default level of optimization enables rather aggressive forms of floating-point optimization that interfere with the correct execution of Cloudy. It is essential to use the "-fp-model source -fp-model except -fp-speculation off" flags in order to disable those optimizations. The following options were used:
     110We tested versions 10.x, 11.x, and 13.0 of icc. The default level of optimization enables rather aggressive forms of floating-point optimization that interfere with the correct execution of Cloudy. It is essential to use the "-fp-model source -fp-model except -fp-speculation off" flags in order to disable those optimizations. The following options were used:
    111111
    112112'''debug compile:'''[[BR]]
     
    126126The icc 9.0 compiler needs an additional parameter "-O0" during the link stage to disable the multi-file optimizer.
    127127
    128 Versions prior to icc 10.0 are not supported. They may not work correctly unless you use lower levels of optimization ("-O1 -mp" or even "-O0"). Make sure you run the test suite if you use such a compiler. Versions 12.0 and 12.1 also need a lower level of optimization (see warning 4 below).
     128Versions prior to icc 10.0 are not supported. They may not work correctly unless you use lower levels of optimization ("-O1 -mp" or even "-O0"). Make sure you run the test suite if you use such a compiler. Versions 12.0 and 12.1 also need a lower level of optimization (see warning 4 below). Version 13.0 works fine again.
    129129
    130130You may get a warning "feupdateenv is not implemented and will always fail" during the link phase. This warning appears to be benign and can be ignored.
     
    136136'''WARNING 3:''' Testing with the C08.00 release has shown that the IA32 version of icc 10.1 is incapable of compiling the code correctly with any level of optimization. We recommend that you use another version of icc, or g++, or the Solaris C++ compiler instead. This problem is ''only'' present on IA32 platforms, and not on any of the 64-bit platforms, and occurs ''only'' with icc 10.1.
    137137
    138 '''WARNING 4:''' Testing on an amd64 platform has shown that icc 12.x produces a broken binary. '''This does not show up when running the smoke test''', but does show up when running the entire test suite. We currently do not have access to the 32-bit version of icc 12.x, so the status for that platform is unknown. Changing "-O3" to "-O1" in the compiler flags produces a valid binary on our 64-bit platforms.
     138'''WARNING 4:''' Testing on an amd64 platform has shown that icc 12.x produces a broken binary. '''This does not show up when running the smoke test''', but does show up when running the entire test suite. The 32-bit version of icc 12.x has not been tested, so the status for that platform is unknown. Changing "-O3" to "-O1" in the compiler flags produces a valid binary on our 64-bit platforms. If you want to use this compiler version, make sure that you lower the optimization level and include '''-DMM''' in the compiler flags to bypass the compiler check built into Cloudy.
    139139
    140140'''icc on Mac''' Apple updated xcode to 3.2.2 in Spring 2010. This upgrade breaks the intel C++ 11.1