[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Intel 2016.1.150 compilation problems

From: Balázs Hajgató
Subject: Re: Intel 2016.1.150 compilation problems
Date: Wed, 16 Mar 2016 22:23:14 +0100

I think i am not able to do that. The case is currently investigated by Intel, lets see what they will get.
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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]