Re: Intel 2016.1.150 compilation problems

[Balázs Hajgató]

I think i am not able to do that. The case is currently investigated by Intel, lets see what they will get.

https://software.intel.com/en-us/forums/intel-c-compiler/topic/612811

Additionally, the previous version of Intel compiler is able to compile the code.

On 16 Mar 2016, at 21:11, Paul Eggert <address@hidden> wrote:

On 03/16/2016 12:04 AM, Balazs Hajgato wrote:

Well, Intel compiler says that C99 or C11 is C, and not C++. So I am not able
to request C99 or C11 for C++ programs.

In that case, why is Gnulib not using the equivalent of "#define restrict /* empty */" so that the rest of the code can use 'restrict' without worrying about this? That is what should happen if your C++ compiler does not support 'restrict' or any of its variant spellings. Please investigate why this substitution isn't happening.