|
From: | Paul Eggert |
Subject: | Re: Intel 2016.1.150 compilation problems |
Date: | Wed, 16 Mar 2016 13:11:46 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
On 03/16/2016 12:04 AM, Balazs Hajgato wrote:
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.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.
[Prev in Thread] | Current Thread | [Next in Thread] |