Setting /permissive- switch on Windows causes some problems.

The code below compiles using the Microsoft Compiler Visual C++ 2017 15.8.2 both with AND without "/permissive-"

However the code fails to compile using Intel Compiler 2018 Update 3 with "/permissive-"

I have encountered many other issues when "/permissive-" is set when using the Intel Compiler.

error : identifier "silly" is undefined
1>      silly tmp = something;
1>      ^
1>          detected during instantiation of class "CDataCacheGetFn<T1, T2, T3> [with T1=double, T2=silly, T3=double]" at line 33
1>
error : expected a ";"
1>      silly tmp = something;
1>            ^
1>          detected during instantiation of class "CDataCacheGetFn<T1, T2, T3> [with T1=double, T2=silly, T3=double]" at line 33

template <class T1, class T2, class T3>
class CDataCacheGetFn
{
public:
	T1 GetFn(const T2 &t2, const T3& t3, void *data)const;
};
struct silly
{

};
double CDataCacheGetFn<double, silly, double>::GetFn(const   silly &something, const double &f, void *)const
{
	silly tmp = something;
	return 1.0;
}

using F = void();

struct X {

  virtual F f;

};
 

struct Y : X {

F f override;

};

The code is valid, but ICC cannot compile the overriden function declaration in Y.

Hi,

I'm developing a library in Visual Studio 2015 for Windows, that is used by IIS. It is compiled in x64 platform.

The version of libmmd.dll (and more dll's from Intel runtime) that are copied to the output directory upon compilation is the x86 version instead of the x64 ones.

Strangely enough this works usually, but when the library can not be loaded by IIS.

When I manually copy to the IIS bin library the correct, x64 version of the dlls from Intel installation bin folder - every thing works fine..

What am I doing wrong upon compilation??

Thanks,

Boaz.

We have some C code that employs exp() and ln() a lot for some test data. Now if we switch the optimization level from O2 to O3, then the code does not work in some cases. It is like the ln() and exp() is less accurate.

In cases where exp() and ln() are not used it works with O3. Is that to be expected?

Erling

I'm having an issue compiling a template class using a newer C++ compiler (going from Visual C++ 6.0 to Visual C++ 2015). All of the errors center around a handful of typedefs within the class. Here is a snippet of the header file:

template< class Type> class Vector
{
public:

    typedef Type* iterator;
    typedef const Type* const_iterator;
    typedef Type& reference;
    typedef const Type& const_reference;
    typedef size_t size_type;

    Vector();
    Vector( size_type Size, const_reference Object = Type() );
...
private:
    VectorImpl<Type>* m_pImpl;
};

template <typename Type> Vector<Type>::Vector()
{
    m_pImpl = new VectorImpl<Type>();
};

template <typename Type> Vector<Type>::Vector(Vector<Type>::size_type Size, Vector<Type>::const_reference Object)
{
    m_pImpl = new VectorImpl<Type>(Size, Object);
};

When the compiler attempts to build the template method implementation it throws an error when encountering the typedef parameter (i.e. 'Vector<Type>::size_type Size') I get an 'C2988 unrecognizable template declaration/definition' error. In other instances I get an 'C2061 syntax error: identifier 'size_type'' error.

Is there a formatting issue or could there be a compatibility issue with using typedefs in a template class?

#include <string>
#include <cassert>

class HelloClass
{
    template<class ...Names>
    void set_names(std::string, Names ...cols) {
        set_names(std::forward<Names>(cols)...);
    }

    void set_names() {
    }

public:
    template<class ...Names>
    void set_function(Names ...cols) {
        set_names(std::forward<Names>(cols)...);
    }
};

int main()
{
    HelloClass hello;
    // this call takes 237 parameters
    hello.set_function("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","32","33","34","35","36","37","38","39","40","41","42","43","44","45","46","47","48","49","50","51","52","53","54","55","56","57","58","59","60","61","62","63","64","65","66","67","68","69","70","71","72","73","74","75","76","77","78","79","80","81","82","83","84","85","86","87","88","89","90","91","92","93","94","95","96","97","98","99","100","101","102","103","104","105","106","107","108","109","110","111","112","113","114","115","116","117","118","119","120","121","122","123","124","125","126","127","128","129","130","131","132","133","134","135","136","137","138","139","140","141","142","143","144","145","146","147","148","149","150","151","152","153","154","155","156","157","158","159","160","161","162","163","164","165","166","167","168","169","170","171","172","173","174","175","176","177","178","179","180","181","182","183","184","185","186","187","188","189","190","191","192","193","194","195","196","197","198","199","200","201","202","203","204","205","206","207","208","209","210","211","212","213","214","215","216","217","218","219","220","221","222","223","224","225","226","227","228","229","230","231","232","233","234","235","236","237");
    return 0;
}

Hello,
I experienced build errors shown below with the icpc version of 18.0.0 20170811.

          ": internal error: ** The compiler has encountered an unexpected problem.

** Segmentation violation signal raised. **

Access violation or stack overflow. Please contact Intel Support for assistance.

 

icpc: error #10014: problem during multi-file optimization compilation (code 4)

Question> Is there a workaround that I can use so that the code can pass the build with this version?

Thank you

I want to receive a copy of my license file please, because I need it to install my server license.

Hello,

I use Intel Compiler to optimize simple loop:

void InitOmegaArrays(float* mCOmega, float* mSOmega, float* mI, int numRows, int numCols, float paramOmega) {

	int ii;

#ifdef __GCC__
#pragma omp parallel for simd
#pragma vector aligned always
#pragma ivdep
#else
#pragma omp parallel for
#endif
	for (ii = 0; ii < numRows * numCols; ii++)
	{
		mCOmega[ii] = cosf(paramOmega * mI[ii]);
		mSOmega[ii] = sinf(paramOmega * mI[ii]);
	}

}

I use the /fp:fast=2 flag.
As expected ICC uses SVML (Even use `sincos()`) yet it creates a dependency on svml_dispmd.dll.

Is there a way to prevent this dependency and make it link the SVML function statically?

I'm using Intel Compiler (ICC) 18.

Thank You.

Hi,

I'm using system studio 2019 beta ultimate on Fedora 27 and Core i7 4790K for BOINC project Citizen Science Grid.

Stock (standard0 software is compiled with g++-7 (probably) with sse3 options.  So I'm trying to compile faster software.  With "-ipo -xCORE-AVX2 -O3 -fp-model fast=1" option, the application runs faster than the stock one, but accuracy is insufficient.   If I changed the options to "-ipo -xCORE-AVX2 -O3 -fp-model precise", the application is slower than the stock, while accuracy is sufficient.

So what should I try next?   Now I'm trying "-ipo -xCORE-AVX2 -O3 -fp-model fast=1 -prec-div -prec-sqrt", but I'm not sure the accuracy is good enough and want to know other ways to obtain better accuracy.  The result will come out in a few days.   It takes many hours to complete one calculation.

Thanks in advance!

-Tetsuji

Hi,

I'm trying to build the latest version of openmpi (3.1.2) using intel 18.0.3 and the installation process complains about the compiler not being ISO C99. The error occurs for other versions of openmpi and intel (18.0.0 and 17).

Also, for what it's worth, I'm using the Fedora 28 with

1
$ uname -r

2
4.17.19-200.fc28.x86_64

3
$ ldd --version

4
ldd (GNU libc) 2.27

I've wrote the following simple build script which download openmpi-3.1.2, extract files and build it.

01
#!/bin/bash

02
set -e

03
INTEL_HOME="<path>"

04
source ${INTEL_HOME}/compilers_and_libraries_2018.3.222/linux/bin/compilervars.sh intel64

05
ifort -v

06
wget https://www.open-mpi.org/software/ompi/v3.1/downloads/openmpi-3.1.2.tar.gz

07
tar -xzvf openmpi-3.1.2.tar.gz

08
TopDir=${pwd}

09
mkdir -p build

10
cd build

11
./../openmpi-3.1.2/configure --prefix=${TopDir}/install CC=icc CXX=icpc FC=ifort CFLAGS="-D_Float128=__float128"

12
make all install -j

You just have to set the path where intel tools are installed in the variable INTEL_HOME.

Running this script, I have the following output:

001
checking for perl... perl

002
 

003
============================================================================

004
== Configuring Open MPI

005
============================================================================

006
 

007
*** Startup tests

008
checking build system type... x86_64-unknown-linux-gnu

009
checking host system type... x86_64-unknown-linux-gnu

010
checking target system type... x86_64-unknown-linux-gnu

011
checking for gcc... icc

012
checking whether the C compiler works... yes

013
checking for C compiler default output file name... a.out

014
checking for suffix of executables...

015
checking whether we are cross compiling... no

016
checking for suffix of object files... o

017
checking whether we are using the GNU C compiler... yes

018
checking whether icc accepts -g... yes

019
checking for icc option to accept ISO C89... none needed

020
checking whether icc understands -c and -o together... yes

021
checking how to run the C preprocessor... icc -E

022
checking for grep that handles long lines and -e... /usr/bin/grep

023
checking for egrep... /usr/bin/grep -E

024
checking for ANSI C header files... yes

025
checking for sys/types.h... yes

026
checking for sys/stat.h... yes

027
checking for stdlib.h... yes

028
checking for string.h... yes

029
checking for memory.h... yes

030
checking for strings.h... yes

031
checking for inttypes.h... yes

032
checking for stdint.h... yes

033
checking for unistd.h... yes

034
checking minix/config.h usability... no

035
checking minix/config.h presence... no

036
checking for minix/config.h... no

037
checking whether it is safe to define __EXTENSIONS__... yes

038
checking for a BSD-compatible install... /usr/bin/install -c

039
checking whether build environment is sane... yes

040
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p

041
checking for gawk... gawk

042
checking whether make sets $(MAKE)... yes

043
checking for style of include used by make... GNU

044
checking whether make supports nested variables... yes

045
checking whether UID '1000' is supported by ustar format... yes

046
checking whether GID '1000' is supported by ustar format... yes

047
checking how to create a ustar tar archive... gnutar

048
checking dependency style of icc... gcc3

049
checking whether make supports nested variables... (cached) yes

050
 

051
*** Checking versions

052
checking for repo version... v3.1.2

053
checking Open MPI version... 3.1.2

054
checking Open MPI release date... Aug 22, 2018

055
checking Open MPI repository version... v3.1.2

056
checking for repo version... v3.1.2

057
checking Open MPI Run-Time Environment version... 3.1.2

058
checking Open MPI Run-Time Environment release date... Aug 22, 2018

059
checking Open MPI Run-Time Environment repository version... v3.1.2

060
checking for repo version... v3.1.2

061
checking Open SHMEM version... 3.1.2

062
checking Open SHMEM release date... Aug 22, 2018

063
checking Open SHMEM repository version... v3.1.2

064
checking for repo version... v3.1.2

065
checking Open Portable Access Layer version... 3.1.2

066
checking Open Portable Access Layer release date... Aug 22, 2018

067
checking Open Portable Access Layer repository version... v3.1.2

068
checking for bootstrap Autoconf version... 2.69

069
checking for bootstrap Automake version... 1.15

070
checking for boostrap Libtool version... 2.4.6

071
 

072
*** Initialization, setup

073
configure: builddir: /home/geek/Applications/OPENMPI/tmp/build

074
configure: srcdir: /home/geek/Applications/OPENMPI/tmp/openmpi-3.1.2

075
configure: Detected VPATH build

076
installing to directory "/install"

077
 

078
*** OPAL Configuration options

079
checking if want to run code coverage... no

080
checking if want to compile with branch probabilities... no

081
checking if want to debug memory usage... no

082
checking if want to profile memory usage... no

083
checking if want developer-level compiler pickyness... no

084
checking if want developer-level debugging code... no

085
checking if want to developer-level timing framework... no

086
checking if want to install project-internal header files... no

087
checking if want pretty-print stacktrace... yes

088
checking if want pty support... yes

089
checking if want weak symbol support... yes

090
checking if want dlopen support... yes

091
checking for default value of mca_base_component_show_load_errors... enabled by default

092
checking if want heterogeneous support... no

093
checking if word-sized integers must be word-size aligned... yes

094
checking if want IPv6 support... no

095
checking if want package/brand string... Open MPI blopez@deimos Distribution

096
checking if want ident string... 3.1.2

097
checking if want to use an alternative checksum algo for messages... no

098
checking maximum length of processor name... 256

099
checking maximum length of error string... 256

100
checking maximum length of object name... 64

101
checking maximum length of info key... 36

102
checking maximum length of info val... 256

103
checking maximum length of port name... 1024

104
checking maximum length of datarep string... 128

105
checking if want getpwuid support... yes

106
checking for zlib in... (default search paths)

107
checking zlib.h usability... no

108
checking zlib.h presence... yes

109
configure: WARNING: zlib.h: present but cannot be compiled

110
configure: WARNING: zlib.h:     check for missing prerequisite headers?

111
configure: WARNING: zlib.h: see the Autoconf documentation

112
configure: WARNING: zlib.h:     section "Present But Cannot Be Compiled"

113
configure: WARNING: zlib.h: proceeding with the compiler's result

114
configure: WARNING:     ## ------------------------------------------------------ ##

115
configure: WARNING:     ## Report this to http://www.open-mpi.org/community/help/ ##

116
configure: WARNING:     ## ------------------------------------------------------ ##

117
checking for zlib.h... no

118
checking will zlib support be built... no

119
checking __NetBSD__... no

120
checking __FreeBSD__... no

121
checking __OpenBSD__... no

122
checking __DragonFly__... no

123
checking __386BSD__... no

124
checking __bsdi__... no

125
checking __APPLE__... no

126
checking __linux__... yes

127
checking __sun__... no

128
checking __sun... no

129
checking netdb.h usability... no

130
checking netdb.h presence... yes

131
configure: WARNING: netdb.h: present but cannot be compiled

132
configure: WARNING: netdb.h:     check for missing prerequisite headers?

133
configure: WARNING: netdb.h: see the Autoconf documentation

134
configure: WARNING: netdb.h:     section "Present But Cannot Be Compiled"

135
configure: WARNING: netdb.h: proceeding with the compiler's result

136
configure: WARNING:     ## ------------------------------------------------------ ##

137
configure: WARNING:     ## Report this to http://www.open-mpi.org/community/help/ ##

138
configure: WARNING:     ## ------------------------------------------------------ ##

139
checking for netdb.h... no

140
checking netinet/in.h usability... no

141
checking netinet/in.h presence... yes

142
configure: WARNING: netinet/in.h: present but cannot be compiled

143
configure: WARNING: netinet/in.h:     check for missing prerequisite headers?

144
configure: WARNING: netinet/in.h: see the Autoconf documentation

145
configure: WARNING: netinet/in.h:     section "Present But Cannot Be Compiled"

146
configure: WARNING: netinet/in.h: proceeding with the compiler's result

147
configure: WARNING:     ## ------------------------------------------------------ ##

148
configure: WARNING:     ## Report this to http://www.open-mpi.org/community/help/ ##

149
configure: WARNING:     ## ------------------------------------------------------ ##

150
checking for netinet/in.h... no

151
checking netinet/tcp.h usability... no

152
checking netinet/tcp.h presence... yes

153
configure: WARNING: netinet/tcp.h: present but cannot be compiled

154
configure: WARNING: netinet/tcp.h:     check for missing prerequisite headers?

155
configure: WARNING: netinet/tcp.h: see the Autoconf documentation

156
configure: WARNING: netinet/tcp.h:     section "Present But Cannot Be Compiled"

157
configure: WARNING: netinet/tcp.h: proceeding with the compiler's result

158
configure: WARNING:     ## ------------------------------------------------------ ##

159
configure: WARNING:     ## Report this to http://www.open-mpi.org/community/help/ ##

160
configure: WARNING:     ## ------------------------------------------------------ ##

161
checking for netinet/tcp.h... no

162
checking for struct sockaddr_in... no

163
checking if --with-cuda is set... not set (--with-cuda=)

164
checking whether CU_POINTER_ATTRIBUTE_SYNC_MEMOPS is declared... no

165
checking whether cuPointerGetAttributes is declared... no

166
checking if have cuda support... no

167
checking if user requested external PMIx support()... no

168
 

169
*** ORTE Configuration options

170
checking if want orterun "--prefix" behavior to be enabled by default... no

171
 

172
*** OMPI Configuration options

173
checking if want compile-time warnings inside of mpi.h... yes

174
checking if want sparse process groups... no

175
checking if want peruse support... no

176
checking if want Fortran MPI bindings...  (try)

177
checking if want C++ bindings... no

178
checking if want MPI::SEEK_SET support... yes

179
checking if want run-time MPI parameter checking... runtime

180
 

181
*** OSHMEM Configuration options

182
checking if want oshmem... yes

183
checking if want SGI/Quadrics compatibility mode... yes

184
checking if want OSHMEM API parameter checking... always

185
checking for on_exit... yes

186
checking if want pshmem... yes

187
checking if want to build OSHMEM fortran bindings... yes

188
checking if want custom libmpi(_FOO) name... mpi

189
checking if want wrapper compiler rpath support... yes

190
checking if want wrapper compiler runpath support... yes

191
 

192
============================================================================

193
== Compiler and preprocessor tests

194
============================================================================

195
 

196
*** C compiler and preprocessor

197
checking for gcc... (cached) icc

198
checking whether we are using the GNU C compiler... (cached) yes

199
checking whether icc accepts -g... (cached) yes

200
checking for icc option to accept ISO C89... (cached) none needed

201
checking whether icc understands -c and -o together... (cached) yes

202
checking for icc option to accept ISO C99... unsupported

203
configure: WARNING: Open MPI requires a C99 compiler

204
configure: error: Aborting

I'm award of this link: https://stackoverflow.com/questions/47313348/open-mpi-with-icc-open-mpi-requires-a-c99-compiler

in which a workaround is given. This workaround consists of adding the options

1
CC=icc CXX=icpc FC=ifort CFLAGS="-D_Float128=__float128"

when running configure but it did not help for me.

Any idea of what is going wrong here ?

Thanks

Hello,

What are the differences between the Intel OpenMP runtime and the one use by LLVM?
According to https://www.openmprtl.org , the Intel C/C++ compilers and LLVM compilers use the same implementation (found here: https://openmp.llvm.org/).
Is it correct? Has it always been right in the past (such as for ICC 2014 and ICC 2016) ?

Thank You.
 

Setting /permissive- switch on Windows causes some problems.

The code below compiles using the Microsoft Compiler Visual C++ 2017 15.8.2 both with AND without "/permissive-"

However the code fails to compile using Intel Compiler 2018 Update 3 with "/permissive-"

I have encountered many other issues when "/permissive-" is set when using the Intel Compiler.

error : identifier "silly" is undefined
1>      silly tmp = something;
1>      ^
1>          detected during instantiation of class "CDataCacheGetFn<T1, T2, T3> [with T1=double, T2=silly, T3=double]" at line 33
1>
error : expected a ";"
1>      silly tmp = something;
1>            ^
1>          detected during instantiation of class "CDataCacheGetFn<T1, T2, T3> [with T1=double, T2=silly, T3=double]" at line 33

template <class T1, class T2, class T3>
class CDataCacheGetFn
{
public:
	T1 GetFn(const T2 &t2, const T3& t3, void *data)const;
};
struct silly
{

};
double CDataCacheGetFn<double, silly, double>::GetFn(const   silly &something, const double &f, void *)const
{
	silly tmp = something;
	return 1.0;
}

using F = void();

struct X {

  virtual F f;

};
 

struct Y : X {

F f override;

};

The code is valid, but ICC cannot compile the overriden function declaration in Y.

Just Released Intel® Parallel Studio XE 2019! Accelerate Parallel Code—Transform Enterprise to Cloud, & HPC to AI

Boost your parallel application performance on the latest Intel® processors with this new, comprehensive suite of development tools. It includes new high-performance Python* capabilities to speed machine learning, a rapid visual prototyping environment to help you visualize parallelism, a simplified profiling workflow and new platform profiler, and capabilities extend HPC solutions on the path to Exascale, and more.

• Learn more > Blog: What’s New in Intel® Parallel Studio 2019 blog | Release Notes | Intel Parallel Studio XE 2019 site
• Current Users: Upgrade Here
• New users: Download Free Trial

I have a case where I have been using #pragma omp simd lastprivate reduction(), probably not a legitimate combination.  It fails now with 2019 (wrong results, no warning), but it runs as well without the pragma as it did with it in the past.  

I haven't found a way to get rid of the usage #pragma simd firstprivate (which the compiler flags as non-standard) without losing performance.

Compiling the following code:

template <typename T>
struct Outer {
  struct Inner {
    template <typename U>
    Outer<U> foo();
  };
};
template <typename T>
template <typename U>
Outer<U> Outer<T>::Inner::foo() {
  return {};
}

Fails to compile with ICC 19.0.0.117, while it should be correct.
GCC and Clang can compile this without issues.

ICC emits the following compilation errors:

main.cpp(10): warning #2357: "Outer<U>" cannot be specified in a template member definition -- "Outer<T>" assumed instead
  Outer<U> Outer<T>::Inner::foo() {
  ^

main.cpp(10): error: declaration is incompatible with function template "Outer<U> Outer<T>::Inner::foo<U>()" (declared at line 5)
  Outer<U> Outer<T>::Inner::foo() {
                            ^

compilation aborted for main.cpp (code 2)

Hello,

I have a simple loop as following:

#pragma omp parallel for
__assume_aligned(mO, 32);
__assume(numColsPad % 32 == 0);
__assume_aligned(vO, 32);
for (ii = 0; ii < numRows; ii++)
	{
		memcpy(&mO[ii * numColsPad], vO, numCols * sizeof(float));
	}

Though I tell the compiler all information needed to use the optimized memcpy it complains the destination should be aligned.
Is there a way to tell it that mO[ii * numColsPad] is aligned for any ii within any thread?

I tried to install 2018 update 3 and 2019 versions on Windows 10 but both installations freeze. Pressing cancel button does not help either, end up to reboot the machine.

Attaching screenshot of a frozen installer and log files.

I need help with this error.
Using source file including <math.h>, the include hierarchy is

bands.c
Note: including file: ../opus-1.3-rc2/win32/config.h
Note: including file:  .\version.h
Note: including file: D:\develop\Intel\compilers_and_libraries_2019.0.117\windows\compiler\include\math.h
Note: including file:  D:\Microsoft\Visual Studio 2013\VC\include\math.h
Note: including file:   D:\Microsoft\Visual Studio 2013\VC\include\crtdefs.h
Note: including file:    D:\Microsoft\Visual Studio 2013\VC\include\sal.h
Note: including file:     D:\Microsoft\Visual Studio 2013\VC\include\ConcurrencySal.h
Note: including file:    D:\Microsoft\Visual Studio 2013\VC\include\vadefs.h
Note: including file:  D:\develop\Intel\compilers_and_libraries_2019.0.117\windows\compiler\include\math_common_define.h

D:\develop\Intel\compilers_and_libraries_2019.0.117\windows\compiler\include\math.h(695): error #1739: redeclaration cannot add dllexport/dllimport to "ldexpf" (declared at line 721 of "D:\Microsoft\Visual Studio 2013\VC\include\math.h")
   _LIBIMF_EXTERN_C float    _LIBIMF_PUBAPI ldexpf( float __x, int __exp );
                                            ^

Here when the parsing returns back to Intel's math.h, the redeclared ldexpf in MSC native header is in some collision
My question is how to bypass the error.
The full compiler params are

D:\develop\Intel\compilers_and_libraries_2019.0.117\windows\\bin\intel64\icl /nologo /GF /MD /LD /W0 /Qlocation,link,"D:\Microsoft\Visual Studio 2013\VC\bin\amd64\link.exe" /Qlocation,masm,"D:\Microsoft\Visual Studio 2013\VC\bin\amd64\ml64.exe" /Qoption,c,--arg_dep_lookup /Qwd69 /Qvc12 /Ox /fp:extended /Qfp-speculation:safe /MP /O3 /Qipo /QxHost /fp:extended /Qfp-speculation:safe /DNDEBUG=1 /D_WIN32_IE=0x090B /D_WINDOWS=1 /DWINVER=0x0603 /D_WIN32_WINDOWS=0x0603 /D_WIN64=1 /DWIN64=1 /DWIN32=1 /D_WIN32_WINNT=0x0603 /D__NT__=0x0603 /D_WINDLL=1 /D_USRDLL=1 /Dinline=__inline /DPREFIX=\"D:/develop/GNU\" /DEXEC_PREFIX=\"D:/develop/GNU\" /DBINDIR=\"D:/develop/GNU/bin\" /DSBINDIR=\"D:/develop/GNU/sbin\" /DLIBEXECDIR=\"D:/develop/GNU/libexec\" /DDATADIR=\"D:/develop/GNU/share\" /DINCLUDEDIR=\"D:/develop/GNU/include\" /DLIBDIR=\"D:/develop/GNU/lib\" /DSYSCONFDIR=\"D:/develop/GNU/etc\" /DSHAREDSTATEDIR=\"D:/develop/GNU/com\" /DLOCALSTATEDIR=\"D:/develop/GNU/var\" /DLOCALEDIR=\"D:/develop/GNU/share/locale\" /DINFODIR=\"D:/develop/GNU/info\" /DMANDIR=\"D:/develop/GNU/man\" /DDOCDIR=\"D:/develop/GNU/doc\" /DEMACSDIR=\"D:/develop/GNU/emacs\" /DOLDINCLUDEDIR=\"/usr/include\" /DPACKAGE=\"opus\" /DPACKAGE_NAME=\"opus\" /DPACKAGE_TARNAME=\"opus\" /DPACKAGE_VERSION=\"1.0\" /D"PACKAGE_STRING=\"opus 1.0\"" /DPACKAGE_BUGREPORT=\"bug-opus@gnu.org\" /DPACKAGE_URL=\"http://www.opus-codec.org/\" /DPKGDATADIR=\"D:/develop/GNU/share/opus\" /DPKGLIBDIR=\"D:/develop/GNU/lib/opus\" /DPKGINCLUDEDIR=\"D:/develop/GNU/include/opus\" /DVERSION=PACKAGE_VERSION /DHAVE_CONFIG_H /DENABLE_EXPERIMENTAL_AMBISONICS /DDLL_EXPORT /DENABLE_EXPERIMENTAL_AMBISONICS /U_DEBUG /UFIXED_POINT /I./win32 /I. /I./include /I./celt /I./silk /I./silk/float /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\compiler\include\icc /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\compiler\include\intel64 /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\compiler\include /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\mkl\include /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\mkl\include\fftw /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\mkl\include\intel64 /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\ipp\include /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\tbb\include /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\pstl\include /ID:\develop\Intel\compilers_and_libraries_2019.0.117\windows\daal\include /I"D:\Microsoft\Visual Studio 2013\VC\include" /ID:\Microsoft\SDKs\Windows\8.1\include\um /ID:\Microsoft\SDKs\Windows\8.1\include\shared /ID:\Microsoft\SDKs\Windows\8.1\include /c /Fo./celt/ ./celt/bands.c ./celt/celt.c ./celt/celt_decoder.c ./celt/celt_encoder.c ./celt/celt_lpc.c ./celt/cwrs.c ./celt/entcode.c ./celt/entdec.c ./celt/entenc.c ./celt/kiss_fft.c ./celt/laplace.c ./celt/mathops.c ./celt/mdct.c ./celt/modes.c ./celt/pitch.c ./celt/quant_bands.c ./celt/rate.c ./celt/vq.c

I  also remark that $(ICInstallDir)\include\icc needs to be included in incpath to prefere Intel's xmmintrin.h. The replacement is not automatic as Intel's header file is in icc\ subfolder not prefixed anywhere. Is this intentional?

Dear sir,
I have got an academic licence for intel parallel studio under linux with a valid serial number (floating licence for a classroom).

When I tried to activate this licence by introducing host id and port numbers, via the intel website, the website was not responding. After few minutes, I get the following error message when I click on the licence number:

"Error
Sequence contains no elements
"

Could you help me please ? I would like to activate the licence and receive the licence file to install it in our machine room.

Also, we used to use vTune in our class, but it seems that this tool is no longer proposed for a free academic licence under Macos and linux, am I wrong ?

Regards