Known Issues

Workaround for interoperability issue with Symantec* Endpoint Client Protection software older than 12.1.2015.2015 for Intel(R) Advisor XE 2013 survey and Intel(R) VTune(TM) Amplifier XE 2013 hotspot analyses

Problem

Intel(R) Advisor XE 2013 Survey and Intel(R) VTune(TM) Amplifier XE 2013 hotspot analyses fails when running on a system with Symantec* Endpoint Client Protection software versions older than 12.1.2015.2015 (For ex: 12.1.1000.157).

Symptoms

As soon as analysis is started, Application Under Test crashes experiences a crash or other sorts of failures. Our tools may report one or more of the following error messages:

  • Microsoft Windows* (XP, Vista, 7)
  • Intel® Advisor XE
  • Intel® VTune™ Amplifier XE
  • MPI sets LD_LIBRARY_PATH incorrectly on Xeon Phi™ under LSF*

    Symptom

    Shared libraries are not found when running a rank on a Xeon Phi™ coprocessor.

    error while loading shared libraries: lib*.so: cannot open shared object file: No such file or directory

    Cause

    When launching a job running in either native or symmetric mode, ranks launched on Xeon Phi" coprocessors under the LSF* job scheduler will not correctly set LD_LIBRARY_PATH.  Instead, the default LD_LIBRARY_PATH for the coprocessor will be used.  If shared libraries are located in other locations, they will not be found.

  • Developers
  • Linux*
  • Server
  • Intermediate
  • Intel® MPI Library
  • Intel® Cluster Studio XE
  • Message Passing Interface
  • LSF
  • HYDRA
  • LD_LIBRARY_PATH
  • Intel® Many Integrated Core Architecture
  • Безопасность, безопасность! А вы её тестируете?

    В коде программ нет мест, где нельзя допустить ошибку. Ошибка может быть в самом простом месте. Если алгоритмы, механизмы обмена данными и интерфейсы люди привыкли тестировать, то с безопасностью всё обстоит гораздо хуже. Часто она реализуется по остаточному принципу. Программист думает, вот сейчас пару строк напишу, и всё будет хорошо. И даже тестировать не надо. Код слишком прост, чтобы допустить в нем ошибку! А вот и нет. Раз занимаетесь безопасностью и пишите какой-то код для этого, то тестируйте его не менее тщательно!

    OMP_PROC_BIND is now supported on compatible non-Intel processors

    The newest versions of the Intel® C++ and Fortran compilers now support OpenMP* environment variable OMP_PROC_BIND on compatible non-Intel processors for Linux* and Windows* platforms.  The compilers containing the fixes are Intel® Composer XE 2011 Update 13 and Intel® Composer XE 2013 Update 1.  Previous versions of these compilers do not support OMP_PROC_BIND, as defined by the OpenMP* Version 3.1 API specification, on non-Intel processors.  Setting OMP_PROC_BIND={true, false} on a non-Intel processor and running a program linked against the Intel® OpenMP* runtime

  • Developers
  • Professors
  • Students
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Business Client
  • Server
  • C/C++
  • Fortran
  • Intermediate
  • Intel® C++ Composer XE
  • Intel® Fortran Composer XE
  • Intel® Visual Fortran Composer XE
  • OMP_PROC_BIND
  • GOMP_CPU_AFFINITY
  • OpenMP*
  • Parallel Computing
  • Gaming Piracy - Separating Fact from Fiction

    I’m sure most of us have all seen and heard the news recently that’s flared up again on Gaming Piracy and DRM issues.   I’d like to address what I feel is one of the most misunderstood, and taken out of context issues that’s plagued this industry for years; and it’s time to put a put a nail in the coffin on this issue.   PC gaming is not being pirated to the tune of 90% by any stretch of the definition.

    Problem: Fortran source files not compiled when building in Visual Studio

    This article provides a solution for the problem of, when in Microsoft Visual Studio, a Fortran source file cannot be compiled (no Compile option when right clicked) or when building a Fortran project, Fortran source files are skipped over. If errors are reported when compiling Fortran sources, this article does not apply.

    First, verify that your Fortran source files have a file type that is recognized by Intel Visual Fortran.  These are:

  • Microsoft Windows* (XP, Vista, 7)
  • Fortran
  • Intel® Visual Fortran Composer XE
  • VersionSpecific
  • Subscribe to Known Issues