Can anyone help with this?  I am porting a legacy c program from UNIX Tru64 to Intel64.  I have not had any luck in mapping the following options:
-source_listing
-assume noaligned_objects
-D_INLINE_INTRINSICS
-show source, header, statistics   

The complete compile options line is as follows:
Tru64
-source_listing -show source,header,statistics -assume noaligned_objects -O0 -D_INLINE_INTRINSICS

Intel64
-O0
I believe some of these I can do without i.e., -source-listing.  I can always cat the code to a .l file.   But I'm not sure about the others.

Hi, 

I keep my Intel C compiler 2013 until recently. A few days ago I bought the 2017 version. The Intel C 2017 is integrated with VS 2015, Community Edition. 

I frequently use functions such as sincos() and sincosf().  With Intel C 2013, it is OK. But when I use the new compiler it complains for lack of prototipe, at compilation time, but after that the linker correctly find and link the symbol. The include of Intel Math library is present:

#include <mathimf.h>

And the language is specified as :  /Qstd=c99.   Were sincos() and sincosf() removed form mathimf.h ?

Thanks ,

Armando

I am porting legacy c applications from tru64 to LINUX.   I need to debug some of these codes and am stumbling along trying to understand the debuggers I can use.  I was told INTEL no longer uses idb, but gdb-ia.  I assume that's a gnu debugger used on an INTEL platform.

I have created a simple c application called Helloworld.   I want to debug the application.   When attempting to debug the simple application, the following occurs:

$>gdb-ia helloworld
$>ImportError: No module named site

or

$>gdb-ia /home/hdjm/project/hello/helloworld
$>ImportError: No module named site

I downloaded a gdb.pdf and searched for the error and got no hits.  Can anyone help with this?

I have Visual Studio 2017 version 15.2 and Parallel Studio XE 2017 Update 4, after getting linker errors the other day I repaired visual studio and all was fine but now I open the same project to find the error LNK1104: cannot open file 'libucrt.lib', a non-existent file, can someone please explain what's going on?

hi

I am getting the following unresolved externs

Using Microsoft header <iostream> with the intel compiler and I have to link with intel .libs is there anything comparable with the intel compiler for iiostream  

error LNK2019: unresolved external symbol "public: __cdecl std::_Lockit::_Lockit(int)" (??0_Lockit@std@@QEAA@H@Z) referenced in function "public: void __cdecl std::_Container_base12::_Orphan_all(void)" (?_Orphan_all@_Container_base12@std@@QEAAXXZ)
1>MyExcHandler.lib(myexchandler.obj) : error LNK2001: unresolved external symbol "public: __cdecl std::_Lockit::_Lockit(int)" (??0_Lockit@std@@QEAA@H@Z)

As defined in IEEE-754 comparisons with NAN should always yield false, this works:

#define __STDC_WANT_DEC_FP__
#include <dfp754.h>

if (0.4dd > nand64("")) {
        return 1;
}
return 0;

Now, __builtin_expect is to give advice to the compiler about the outcome of a boolean expression, it shouldn't change the code path at all, however it does:

#define __STDC_WANT_DEC_FP__
#include <dfp754.h>

if (__builtin_expect(0.4dd > nand64(""), 0)) {
        return 1;
}
return 0;

This snippet compiled with icc (ICC) 17.0.4 20170411 will now return 1.

I've downloaded a project through SVN. I've downloaded and installed Parallel Studio 2017. And I have Visual Studio 2015. 

I changed my project's platform toolset to Intel C++ Compiler 17. In the solution explorer it says "(Intel C++ Compiler 17.0). But when trying to  build project, it goes well for sometime and at same file everytime it fails and still says: 

Error MSB8020 The build tools for Intel C++ Compiler XE 15.0 (Platform Toolset = 'Intel C++ Compiler XE 15.0') cannot be found. To build using the Intel C++ Compiler XE 15.0 build tools, please install Intel C++ Compiler XE 15.0 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". ArmageddonGame C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Platform.targets 57

I'm a beginner on Visual Studio and C++. What am I doing wrong?

Hello,

I am a student which I have successfully qualified for academic licence. I would like to use Intel C++ compiler in conjuction to IntelMPI. I have installed (as root user) Intel Parallel Studio under /home/intel (because I didn't have enough free space in / ). Afterwards, I run

source /home/intel/compilers_and_libraries_2017.4.196/linux/bin/compilervars.sh intel64

as root user (compilervars.sh failed and I should run under source).

Up to now, everything seems ok. LD_LIBRARY_PATH is set and I can compile programs as I should do. But when I return to an ordinary (non root) user, the enviromental variables are not set. So, I include in the ~/.bashrc file the following lines

PATH=".:$PATH:/home/intel/compilers_and_libraries_2017.4.196/linux/bin/intel64:/home/intel//compilers_and_libraries_2017.4.196/linux/mpi/intel64/bin:/home/intel/debugger_2017/gdb/intel64_mic/bin:/home/intel/compilers_and_libraries_2017.4.196/linux/bin/intel64:/home/intel//compilers_and_libraries_2017.4.196/linux/mpi/intel64/bin:/home/intel/debugger_2017/gdb/intel64_mic/bin"
export LD_LIBRARY_PATH=/home/intel/compilers_and_libraries_2017.4.196/linux/compiler/lib/intel64:/home/intel/compilers_and_libraries_2017.4.196/linux/compiler/lib/intel64_lin:/home/intel//compilers_and_libraries_2017.4.196/linux/mpi/intel64/lib:/home/intel//compilers_and_libraries_2017.4.196/linux/mpi/mic/lib:/home/intel/compilers_and_libraries_2017.4.196/linux/compiler/lib/intel64_lin:/home/intel/compilers_and_libraries_2017.4.196/linux/mkl/lib/intel64_lin:/home/intel/compilers_and_libraries_2017.4.196/linux/tbb/lib/intel64/gcc4.7:/home/intel/debugger_2017/iga/lib:/home/intel/debugger_2017/libipt/intel64/lib:/home/intel/compilers_and_libraries_2017.4.196/linux/compiler/lib/intel64:/home/intel/compilers_and_libraries_2017.4.196/linux/compiler/lib/intel64_lin:/home/intel//compilers_and_libraries_2017.4.196/linux/mpi/intel64/lib:/home/intel//compilers_and_libraries_2017.4.196/linux/mpi/mic/lib:/home/intel/compilers_and_libraries_2017.4.196/linux/compiler/lib/intel64_lin:/home/intel/compilers_and_libraries_2017.4.196/linux/mkl/lib/intel64_lin:/home/intel/compilers_and_libraries_2017.4.196/linux/tbb/lib/intel64/gcc4.7:/home/intel/debugger_2017/iga/lib:/home/intel/debugger_2017/libipt/intel64/lib

source /home/intel/compilers_and_libraries_2017/linux/bin/compilervars.sh intel64

From now on, the mpiicpc, icc etc points to the right point. But mpirun is not the Intel's MPI but the MVAPICH2 installation which comes bundle with debian and Gnu. As root user, the mpirun points to the correct intel's executable.

What should I do in order to be able to use as a user (not root) the Intel C++ compiler and IntelMPI without explicitly set the enviromental variables? In the case of the mpirun, this should point to the correct one and maybe an enviromental variable will be needed there (to switch between MVAPICH2 and IntelMPI).

Thank you in advance

Hi, All!

I have a board with intel atom E3845. This processor has a I2C controller. I setup a driver for windows7 64bit, and I want write a some code.  I cannot find any documentations or examples about how to use I2C controller in windows7. 

May be anybody has tried use I2C bus on this processor?

Thanks

Is there a reason that __builtin_nand32, __builtin_nand64, __builtin_nand128, __builtin_infd32, __builtin_infd64, __builtin_infd128 aren't exposed in icc, even with gcc compatibility turned on?

While it may seem pedantic, those are needed to initialise globals in C, e.g.:

static _Decimal32 foo = __builtin_infd32();
static _Decimal64 bar = __builtin_nand64("");

In gcc those are considered constant expressions.  GNU libc uses a similar trick to provide NAN and INFINTIY in bits/nan.h and bits/inf.h

I know to work around this one could use

static _Decimal32 foo = (_Decimal32)__builtin_inf();
static _Decimal64 bar = (_Decimal64)__builtin_nan("");

the double equivalent, which is then cast to the target type, but this feels rather hacky.

icc (ICC) 17.0.4 20170411
openSUSE 13.1 (Bottle) (x86_64)
 

I am running on RHE6.7 which comes with gcc 4.4.7. My source code that requires c++11 compatible compiler, so I have downloaded gcc 4.8.2. I am able to compile with gcc 4.8.2 and run.

The Intel compiler completes without any error but when I run the output... I get a segmentation fault. I also get a segmentation fault if I compile HelloWorld.cpp (only when specifying version of 4.8.2), see below:

$ /opt/rh/devtoolset-2/root/usr/bin/g++ HelloWorld.cpp
$ ./a.out
Hello World!

$ icpc HelloWorld.cpp
$ ./a.out
Hello World!

$ icpc -gcc-name=/opt/rh/devtoolset-2/root/usr/bin/gcc HelloWorld.cpp
$ ./a.out
Segmentation fault

Does anyone know what I is happening or what I am doing wrong? Your help will be much appreciated.

I compile project in Visual Studio 2015 with Intel C++ Compiler 17 without any error. Modify some codes and compile again without any errors again.

But when I shutdown the computer and turn on again, compiler fails and throws this into output screen:

1>": : error : ** The compiler has encountered an unexpected problem.
1>  ** Segmentation violation signal raised. **
1>  Access violation or stack overflow. Please contact Intel Support for assistance.
1>
1>  compilation aborted for ..\..\Sources\Shared\UnitTypes.cpp (code 4)

Last line can be anything. It isn't because of UnitTypes.cpp. It can be any class file in later errors. And in error list:

** The compiler has encountered an unexpected problem.   

After that I have to build and compile the whole solution and it takes too much time. Everytime when I shutdown computer and open again, I have to do that.

Running an application that uses MPI, OpenMP tasks in MPI_THREAD_MULTIPLE mode I get this error;

[26] trying to free memory block that is currently involved to uncompleted data transfer  operation

free mem  - addr=0x7fffc40812d0 len=175104
 RTC entry - addr=0x7fffc4081300 len=175056 cnt=1
Assertion failed in file ../../i_rtc_cache.c at line 1408: 0

This has been compiled with Intel 17 and uses Intel MPI 17. 

Any idea of how I could debug this issue?

Regards,

Luis

Just Tried to build TF with icc and it keeps failing. the following is the command used for building:

CC=icc bazel build --verbose_failures --config=mkl --copt=-msse4.2 --copt="-DEIGEN_USE_VML" -c opt //tensorflow/tools/pip_package:build_pip_package

The following was the error output:

INFO: From Compiling tensorflow/contrib/memory_stats/ops/memory_stats_ops.cc [for host]:
icc: command line warning #10006: ignoring unknown option '-frandom-seed=bazel-out/host/bin/tensorflow/contrib/memory_stats/_objs/memory_stats_ops_op_lib/tensorflow/contrib/memory_stats/ops/memory_stats_ops.o'
icc: command line warning #10006: ignoring unknown option '-Wno-builtin-macro-redefined'
Warning #2011: predefined meaning of "__DATE__" discarded

Warning #2011: predefined meaning of "__TIMESTAMP__" discarded

Warning #2011: predefined meaning of "__TIME__" discarded

tensorflow/contrib/memory_stats/ops/memory_stats_ops.cc(29): warning #2196: routine is both "inline" and "noinline"

tensorflow/contrib/memory_stats/ops/memory_stats_ops.cc(29): warning #2196: routine is both "inline" and "noinline"

ERROR: /home/bert/tensorflow/tensorflow/contrib/image/BUILD:20:1: C++ compilation of rule '//tensorflow/contrib/image:python/ops/_image_ops.so' failed: icc failed: error executing command
  (cd /root/.cache/bazel/_bazel_root/de2d5e30e11a47d70dad7109465f3a0a/execroot/org_tensorflow && \
  exec env - \
    PWD=/proc/self/cwd \
    PYTHON_BIN_PATH=/opt/intel/intelpython3/bin/python \
    PYTHON_LIB_PATH=/opt/intel/intelpython3/lib/python3.5/site-packages \
    TF_NEED_CUDA=0 \
    TF_NEED_OPENCL=0 \
  /opt/intel/compilers_and_libraries_2017.4.196/linux/bin/intel64/icc -U_FORTIFY_SOURCE -fstack-protector -Wall -B/opt/intel/compilers_and_libraries_2017.4.196/linux/bin/intel64 -B/usr/bin -Wunused-but-set-parameter -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections -msse4.2 -DEIGEN_USE_VML '-std=c++0x' -MD -MF bazel-out/local-py3-opt/bin/tensorflow/contrib/image/_objs/python/ops/_image_ops.so/tensorflow/contrib/image/kernels/bipartite_match_op.pic.d '-frandom-seed=bazel-out/local-py3-opt/bin/tensorflow/contrib/image/_objs/python/ops/_image_ops.so/tensorflow/contrib/image/kernels/bipartite_match_op.pic.o' -fPIC -DEIGEN_MPL2_ONLY -iquote . -iquote bazel-out/local-py3-opt/genfiles -iquote external/protobuf -iquote bazel-out/local-py3-opt/genfiles/external/protobuf -iquote external/bazel_tools -iquote bazel-out/local-py3-opt/genfiles/external/bazel_tools -iquote external/eigen_archive -iquote bazel-out/local-py3-opt/genfiles/external/eigen_archive -iquote external/local_config_sycl -iquote bazel-out/local-py3-opt/genfiles/external/local_config_sycl -isystem external/protobuf/src -isystem bazel-out/local-py3-opt/genfiles/external/protobuf/src -isystem external/bazel_tools/tools/cpp/gcc3 -isystem third_party/eigen3/mkl_include -isystem bazel-out/local-py3-opt/genfiles/third_party/eigen3/mkl_include -isystem external/eigen_archive -isystem bazel-out/local-py3-opt/genfiles/external/eigen_archive -DEIGEN_AVOID_STL_ARRAY -Iexternal/gemmlowp -Wno-sign-compare -fno-exceptions '-DINTEL_MKL=1' -fopenmp -msse3 -pthread -Wno-builtin-macro-redefined '-D__DATE__="redacted"''-D__TIMESTAMP__="redacted"''-D__TIME__="redacted"' -c tensorflow/contrib/image/kernels/bipartite_match_op.cc -o bazel-out/local-py3-opt/bin/tensorflow/contrib/image/_objs/python/ops/_image_ops.so/tensorflow/contrib/image/kernels/bipartite_match_op.pic.o): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 2.
icc: command line warning #10006: ignoring unknown option '-frandom-seed=bazel-out/local-py3-opt/bin/tensorflow/contrib/image/_objs/python/ops/_image_ops.so/tensorflow/contrib/image/kernels/bipartite_match_op.pic.o'
icc: command line warning #10120: overriding '-msse4.2' with '-msse3'
icc: command line warning #10006: ignoring unknown option '-Wno-builtin-macro-redefined'
Warning #2011: predefined meaning of "__DATE__" discarded

Warning #2011: predefined meaning of "__TIMESTAMP__" discarded

Warning #2011: predefined meaning of "__TIME__" discarded

In file included from tensorflow/contrib/image/kernels/bipartite_match_op.cc(17):
./tensorflow/core/framework/op_kernel.h(317): warning #858: type qualifier on return type is meaningless
    const int graph_def_version() const { return graph_def_version_; }
    ^

tensorflow/contrib/image/kernels/bipartite_match_op.cc(88): error: type name is not allowed
      typename TTypes<float, 2>::ConstTensor distance_mat =
      ^

tensorflow/contrib/image/kernels/bipartite_match_op.cc(88): error: expected a ";"
      typename TTypes<float, 2>::ConstTensor distance_mat =
                                             ^

tensorflow/contrib/image/kernels/bipartite_match_op.cc(98): error: identifier "distance_mat" is undefined
              DistancePair(index1, index2, distance_mat(index1, index2)));
                                           ^

tensorflow/contrib/image/kernels/bipartite_match_op.cc(134): warning #2196: routine is both "inline" and "noinline"

tensorflow/contrib/image/kernels/bipartite_match_op.cc(134): warning #2196: routine is both "inline" and "noinline"

tensorflow/contrib/image/kernels/bipartite_match_op.cc(134): warning #2196: routine is both "inline" and "noinline"

tensorflow/contrib/image/kernels/bipartite_match_op.cc(134): warning #2196: routine is both "inline" and "noinline"

tensorflow/contrib/image/kernels/bipartite_match_op.cc(134): warning #2196: routine is both "inline" and "noinline"

tensorflow/contrib/image/kernels/bipartite_match_op.cc(134): warning #2196: routine is both "inline" and "noinline"

tensorflow/contrib/image/kernels/bipartite_match_op.cc(134): warning #2196: routine is both "inline" and "noinline"

compilation aborted for tensorflow/contrib/image/kernels/bipartite_match_op.cc (code 2)
Target //tensorflow/tools/pip_package:build_pip_package failed to build
INFO: Elapsed time: 93.648s, Critical Path: 18.66s

The issue seems to be with a contrib, is it possible to exclude certain contribs from the compilation? The Python used is intel python 3.5 As bit of background, the system is Ubuntu 16 running on dual x5550, the aim was to get better performance since plain TF on a PC (i7-4700mq) works much faster.

I just reinstalled the XE 2017 compiler with a new installation of VS 2017 Community edition on Window 10 Pro.

It is giving error messages with which I am unfamiliar and cannot find in the help system.

ipo: : error #11023: Not all components required for linking are present on command line
The libraries that I am deliberately using are all accounted for and I am not using the Intel Performance Libraries.
Any idea what this could be or how I can narrow down the possible missing components?

...gtest-port.h(1749) (col. 3): : error : 010101_45097
Couldn't find this error, except for old forum posts about .targets files for VS14 that didn't seem to apply.

Line 1749 referred to is the last line of 

class GTestMutexLock {
 public:
  explicit GTestMutexLock(Mutex* mutex)
      : mutex_(mutex) { mutex_->Lock(); }

  ~GTestMutexLock() { mutex_->Unlock(); }

xilink: : error #10014: problem during multi-file optimization compilation (code 4)
This would be easier to understand if I were using multi-file optimization, but I am using a Debug setting without /Qipo.
Again any way to narrow down the problem?

I was trying to compile Geant4 package with parallel_studio_xe_2017.4.056 software (on Linux), it was working fine however when I tried to compile static libraries it gave me:

geant4.10.02/source/processes/electromagnetic/standard/src/G4PAIxSection.cc(874) (col. 1): internal error: IERROR_MODULE_ID_1204

there is nothing special about line 874 in the quoted file, and it compiles into shared libraries and runs well. I am wondering why static libraries give me this error?

Intel Compiler XE 2017, Windows 64-bit.

Can anyone give some hints as to what this indicates ... Its clearly some kind of OpenMP threading issue that is hard to track. Intel Inspector is not giving me enough clues to find the issue.

This is happening on exit() as the OpenMP library cleans up after itself.

     libiomp5md.dll!__kmp_dephash_free(kmp_info * thread, kmp_dephash * h) Line 138    C++
     libiomp5md.dll!__kmp_free_implicit_task(kmp_info * thread) Line 931    C++
     libiomp5md.dll!__kmp_internal_end() Line 5897    C++
     libiomp5md.dll!__kmp_internal_end_library(int gtid_req) Line 524    C++
     libiomp5md.dll!DllMain(HINSTANCE__ * hInstDLL, unsigned long fdwReason, void * lpReserved) Line 775    C++
>    libiomp5md.dll!__DllMainCRTStartup(void * hDllHandle, unsigned long dwReason, void * lpreserved) Line 330    C

I recently installed VS2017 and Intel XE 2017 and hoped that my existing projects (all Intel C++ 17) would work, but no such luck.

When I open a solution and select Properties for a project, it shows "There are no property pages for the selection".

When I try to change the project to use Visual C++, it says "Object reference not set to an instance of an object"

How can I repair the properties to work with the new version?

Many thanks

Hi,

I use Intel 17.0.4 compiler and Intel Xeon E5 2697 V4 (Broadwell) processor. I know that this processor supports fused multiply add instruction.

For this line of code:

      yy +=  (A[i] * B[i]);

If I convert the C++ code to assembly I can see vfmadd231pd 16(%rdx,%r11,8), %xmm6, %xmm1

However, when I use vYY = _mm256_fmadd_pd (vA, vB, vYY) in the C++ code, the compiler uses add and multiply vector instructions only: 

vmulpd    (%r15,%rsi,8), %ymm4, %ymm5              

vaddpd    %ymm1, %ymm5, %ymm1         

Is there any explanation for this ?

Thanks,

Dear Intel Development Team,

It is a big project, but  Composer XE 2013 SP1.4.237 is able to do /Qipo ok.

On the other hand:  When 2017 compiler finish (without crash) the generated code has problems on some machines without AVX (I compile for SSE3 as base instruction set, with CPU dispatch for AVX if present). The code created with Composer XE 2013 is OK. If the machine has AVX, there is no problem. If I change the optimization to /Qip , the code is OK.

Compiler Error Message:

1>": : error : ** The compiler has encountered an unexpected problem.
1>  ** Segmentation violation signal raised. **
1>  Access violation or stack overflow. Please contact Intel Support for assistance.
1>
1>xilink: : error #10014: problem during multi-file optimization compilation (code 4)
1>xilink: : error #10014: problem during multi-file optimization compilation (code 4)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========