<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Re:Integer arithmetic overflow in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1392070#M28044</link>
    <description>&lt;P&gt;I use the 32bit compiler "classic Borland Compiler" (&amp;lt; C++11) from the current Embarcadero C++ Builder IDE. With this compiler, _WIN32 is defined and because of that, the macro "#define INT64_SUFFIX(name) name##L" (from ipptypes.h) is in effect if you simply do:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Ipp64u xyz=ippCPUID_AVX512IFMA;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;If you remember, ippCPUID_AVX512IFMA is defined in ipptypes.h as "#define ippCPUID_AVX512IFMA INT64_SUFFIX(0x100000000)" and INT64_SUFFIX(0x100000000) would act in this case as "name##L", it is clear, a &amp;lt; C++11 compiler must complain about trying to put a bigger than 32bit integer value (0x100000000) in a 32bit value only ("name##L" instead of "name##LL").&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Such a line causes (in my compiler) the compiler warning: "Integer arithmetic overflow" because it is an compiler &amp;lt; C++11.&lt;BR /&gt;(see also: &lt;A href="https://en.cppreference.com/w/cpp/language/integer_literal" target="_blank"&gt;https://en.cppreference.com/w/cpp/language/integer_literal&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;You probaly use other comilers than me, hence it does not make sense to provide you a small C++ Builder project for reproduction. To see the thing and possibly modify the macros to the better is quite obvious I think and needs not necessarily a project file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jun 2022 14:02:47 GMT</pubDate>
    <dc:creator>Wobo</dc:creator>
    <dc:date>2022-06-13T14:02:47Z</dc:date>
    <item>
      <title>Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1391627#M28041</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;currently using IPP 2021.6.0 for Windows. There I got some compiler warnings when working with a 32bit C++ compiler (&amp;lt; C++11) concerning "integer arithmetic overflow" when using constants defined in ipptypes.h like ippCPUID_AVX512IFMA (or bigger). I found in ipptypes.h a piece of code that seems a bit odd and which is the cause for the compiler warnings:&lt;/P&gt;
&lt;P&gt;#if defined( _WIN32 ) || defined ( _WIN64 )&lt;BR /&gt;#define INT64_SUFFIX(name) name##L&lt;BR /&gt;#else&lt;BR /&gt;#define INT64_SUFFIX(name) name##LL&lt;BR /&gt;#endif&lt;/P&gt;
&lt;P&gt;#define ippCPUID_AVX512IFMA INT64_SUFFIX(0x100000000) /* Intel(R) Advanced Vector Extensions 512 IFMA (PMADD52) instruction set */&lt;BR /&gt;#define ippCPUID_NOCHECK INT64_SUFFIX(0x8000000000000000) /* Force ippSetCpuFeatures to set CPU features without check */&lt;BR /&gt;#define ippCPUID_GETINFO_A INT64_SUFFIX(0x616f666e69746567) /* Force ippGetCpuFeatures to work as cpuid instruction */&lt;BR /&gt;#define ippAVX512_ENABLEDBYOS INT64_SUFFIX(0x200000000) /* Intel(R) Advanced Vector Extensions 512 is supported by OS */&lt;BR /&gt;#define ippCPUID_AVX512VPOPCNTDQ INT64_SUFFIX(0x400000000) /* Intel(R) Advanced Vector Extensions 512 VPOPCNTDQ instruction set */&lt;BR /&gt;#define ippCPUID_AVX512_BITALG INT64_SUFFIX(0x800000000) /* Intel(R) Advanced Vector Extensions 512 BITALG instruction set */&lt;BR /&gt;#define ippCPUID_AVX512_FP16 INT64_SUFFIX(0x1000000000) /* Intel(R) Advanced Vector Extensions 512 16-bit floating point (FP16) instruction set */&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you use a 32bit C++ compiler (_WIN32 is true, until C++11), the line "#define INT64_SUFFIX(name) name##L" tries to put a value ippCPUID_AVX512IFMA (or bigger) that is greater than max unsigned long int (unsigned 32bit integer) into 32bit integer (until C++11), which is impossible and causes an integer arithmetic overflow (at least as a compiler warning, real code depends on what the specific compiler makes of it).&lt;/P&gt;
&lt;P&gt;I used reference: &lt;A href="https://en.cppreference.com/w/cpp/language/integer_literal" target="_blank"&gt;https://en.cppreference.com/w/cpp/language/integer_literal&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;However, a simple solution for me, to get rid of these compiler warnings, is just to hack a bit ipptypes.h in a way that looks like:&lt;/P&gt;
&lt;P&gt;/* #if defined( _WIN32 ) || defined ( _WIN64 )&lt;BR /&gt;#define INT64_SUFFIX(name) name##L&lt;BR /&gt;#else */&lt;/P&gt;
&lt;P&gt;#define INT64_SUFFIX(name) name##LL&lt;/P&gt;
&lt;P&gt;/* #endif */&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The line "#define INT64_SUFFIX(name) name##LL" does it for every purpose, at least for my 32bit and my 64bit compilers.&lt;/P&gt;
&lt;P&gt;Maybe these not so safe macro definitions in ipptypes.h can be improved a bit in a next IPP version, so that this personal quick hack is no longer necessary...&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 12:07:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1391627#M28041</guid>
      <dc:creator>Wobo</dc:creator>
      <dc:date>2022-06-10T12:07:44Z</dc:date>
    </item>
    <item>
      <title>Re:Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1392064#M28043</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you for posting on Intel Communities.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you for sharing the details. Could you please share us a sample reproducer, so that we could try investigating the mentioned compiler warning at our end.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Shanmukh.SS&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Jun 2022 13:22:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1392064#M28043</guid>
      <dc:creator>ShanmukhS_Intel</dc:creator>
      <dc:date>2022-06-13T13:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1392070#M28044</link>
      <description>&lt;P&gt;I use the 32bit compiler "classic Borland Compiler" (&amp;lt; C++11) from the current Embarcadero C++ Builder IDE. With this compiler, _WIN32 is defined and because of that, the macro "#define INT64_SUFFIX(name) name##L" (from ipptypes.h) is in effect if you simply do:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Ipp64u xyz=ippCPUID_AVX512IFMA;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;If you remember, ippCPUID_AVX512IFMA is defined in ipptypes.h as "#define ippCPUID_AVX512IFMA INT64_SUFFIX(0x100000000)" and INT64_SUFFIX(0x100000000) would act in this case as "name##L", it is clear, a &amp;lt; C++11 compiler must complain about trying to put a bigger than 32bit integer value (0x100000000) in a 32bit value only ("name##L" instead of "name##LL").&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Such a line causes (in my compiler) the compiler warning: "Integer arithmetic overflow" because it is an compiler &amp;lt; C++11.&lt;BR /&gt;(see also: &lt;A href="https://en.cppreference.com/w/cpp/language/integer_literal" target="_blank"&gt;https://en.cppreference.com/w/cpp/language/integer_literal&lt;/A&gt;)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;You probaly use other comilers than me, hence it does not make sense to provide you a small C++ Builder project for reproduction. To see the thing and possibly modify the macros to the better is quite obvious I think and needs not necessarily a project file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jun 2022 14:02:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1392070#M28044</guid>
      <dc:creator>Wobo</dc:creator>
      <dc:date>2022-06-13T14:02:47Z</dc:date>
    </item>
    <item>
      <title>Re: Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1394125#M28051</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Meanwhile, we look into your issue further using intel/ intel compatible compilers, We would like to provide you with the list of compilers supported under the below system requirements link.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.intel.com/content/www/us/en/developer/articles/system-requirements/intel-oneapi-intel-integrated-performance-primitives-system-requirements.html" target="_blank" rel="noopener"&gt;https://www.intel.com/content/www/us/en/developer/articles/system-requirements/intel-oneapi-intel-integrated-performance-primitives-system-requirements.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Shanmukh.SS&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 19:10:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1394125#M28051</guid>
      <dc:creator>ShanmukhS_Intel</dc:creator>
      <dc:date>2022-07-14T19:10:42Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1394129#M28052</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;thank you for the link. However, the described issue is not only related to a specific compiler, it is also related to the used C++ standard. For C++ compilers &amp;lt; C++11 the macro is likely to "fail", for C++ starting with C++11, "##L" can also be interpreted as "long long int", see 3rd row in table "Type of the literal" under link: &lt;A href="https://en.cppreference.com/w/cpp/language/integer_literal" target="_blank"&gt;https://en.cppreference.com/w/cpp/language/integer_literal&lt;/A&gt;. In this case the macro will not "fail", respectively the compiler will not issue the mentioned warning.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 11:07:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1394129#M28052</guid>
      <dc:creator>Wobo</dc:creator>
      <dc:date>2022-06-21T11:07:01Z</dc:date>
    </item>
    <item>
      <title>Re: Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1396293#M28056</link>
      <description>&lt;P&gt;Hi Wobo,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are trying to reproduce the issue at our environment. We will get back to you on this with updated and our findings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Shanmukh.SS&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 19:11:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1396293#M28056</guid>
      <dc:creator>ShanmukhS_Intel</dc:creator>
      <dc:date>2022-07-14T19:11:41Z</dc:date>
    </item>
    <item>
      <title>Re: Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1398485#M28061</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you please share us a sample reproducer, so that we could try reproducing the issue and work on it further?&amp;nbsp;&lt;SPAN&gt;as we have an environmental issue at our end to generate the compiler warnings mentioned.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Shanmukh.SS&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 19:13:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1398485#M28061</guid>
      <dc:creator>ShanmukhS_Intel</dc:creator>
      <dc:date>2022-07-14T19:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1398589#M28062</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;my projects/source files are incompatible to your compilers. So it is of no use for you.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;-#define ippCPUID_AVX512IFMA INT64_SUFFIX(0x100000000) /* Intel(R) Advanced Vector Extensions 512 IFMA (PMADD52) instruction set */&lt;BR /&gt;-#define INT64_SUFFIX(name) name##L =&amp;gt; max unsigned long int for compilers less than C++11&lt;BR /&gt;-0x100000000 is bigger than unsigned long int&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;To reproduce/test it, just use this source code line (as can be found already in my post from 06-13-2022):&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Ipp64u xyz=ippCPUID_AVX512IFMA;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;My 32 bit compiler&lt;/STRONG&gt; (Embarcadero 32 bit "classic Borland Compiler", _WIN32 is defined with this compiler) issues a warning "Integer arithmetic overflow" (because of "ippCPUID_AVX512IFMA") because it &lt;STRONG&gt;is a &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;compiler less than C++11, hence it has to do it according to:&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;A href="https://en.cppreference.com/w/cpp/language/integer_literal" target="_blank"&gt;https://en.cppreference.com/w/cpp/language/integer_literal&lt;/A&gt; (l or L =&amp;gt; long int or unsigned long int)&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;and because the macro in effect (from ipptypes.h):&lt;BR /&gt;#if defined( _WIN32 ) || defined ( _WIN64 )&lt;BR /&gt;#define INT64_SUFFIX(name) name##L&lt;BR /&gt;...&lt;/P&gt;
&lt;P&gt;A compiler greater or equal to C++11 will normally not issue such a warning because of &lt;A href="https://en.cppreference.com/w/cpp/language/integer_literal" target="_blank"&gt;https://en.cppreference.com/w/cpp/language/integer_literal&lt;/A&gt;, &lt;STRONG&gt;see table "The type of the literal" row 3&lt;/STRONG&gt; (l or L =&amp;gt; also &lt;BR /&gt;long long int or unsigned long long int).&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;For alle my compilers I use from Embarcadero, the line:&lt;/P&gt;
&lt;P&gt;#define INT64_SUFFIX(name) name##LL&lt;/P&gt;
&lt;P&gt;is good enough to make all things work and silence the 32 bit compiler warning, mentioned in these posts.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have my solution just to patch/hack ipptypes.h macro just to that:&lt;BR /&gt;/* #if defined( _WIN32 ) || defined ( _WIN64 )&lt;BR /&gt;#define INT64_SUFFIX(name) name##L&lt;BR /&gt;#else */&lt;/P&gt;
&lt;P&gt;#define INT64_SUFFIX(name) name##LL&lt;/P&gt;
&lt;P&gt;/* #endif */&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 10:09:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1398589#M28062</guid>
      <dc:creator>Wobo</dc:creator>
      <dc:date>2022-07-07T10:09:45Z</dc:date>
    </item>
    <item>
      <title>Re:Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1400523#M28066</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are able to generate the compiler warning mentioned. We are working on this internally, we will get back to you soon with an update.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Shanmukh.SS&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Jul 2022 02:57:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1400523#M28066</guid>
      <dc:creator>ShanmukhS_Intel</dc:creator>
      <dc:date>2022-07-15T02:57:58Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1400608#M28067</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt;We are able to generate the compiler warning mentioned. We are working on this internally, we will get back&lt;/P&gt;
&lt;P&gt;&amp;gt;&amp;gt;to you soon with an update.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ok, good to know.&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 07:52:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1400608#M28067</guid>
      <dc:creator>Wobo</dc:creator>
      <dc:date>2022-07-15T07:52:03Z</dc:date>
    </item>
    <item>
      <title>Re:Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1415170#M28109</link>
      <description>&lt;P&gt;Hello Wobo,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you to contact to us.&lt;/P&gt;&lt;P&gt;Good to know you have workaround for your own 32-bit compiler.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;For IPP supports compilers list in IPP release notes here: &lt;A href="https://www.intel.com/content/www/us/en/developer/articles/system-requirements/intel-oneapi-intel-integrated-performance-primitives-system-requirements.html" target="_blank"&gt;https://www.intel.com/content/www/us/en/developer/articles/system-requirements/intel-oneapi-intel-integrated-performance-primitives-system-requirements.html&lt;/A&gt;&lt;/P&gt;&lt;H2&gt;&lt;BR /&gt;&lt;/H2&gt;&lt;H2&gt;Supported Compilers&lt;/H2&gt;&lt;H3&gt;Linux*&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Intel® C++ Compiler 19.1 for Linux* OS and later&lt;/LI&gt;&lt;LI&gt;GNU Compilers 4.8 and higher&lt;/LI&gt;&lt;LI&gt;Glibc version 2.4 or higher&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;Windows*&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Intel® C++ Compiler 19.1 for Windows* OS and later&lt;/LI&gt;&lt;LI&gt;Microsoft Visual Studio* 2017 - help file and environment integration&lt;/LI&gt;&lt;LI&gt;Microsoft Visual Studio* 2019 - help file and environment integration&lt;/LI&gt;&lt;LI&gt;Microsoft Visual Studio* 2022 Community, Enterprise and Professional Editions with 'Desktop development with C++' component installed are supported, except for use with Intel® Inspector and Intel® Advisor.&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;macOS*&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Xcode* 10&lt;/LI&gt;&lt;LI&gt;Xcode* 11&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Sep 2022 06:04:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1415170#M28109</guid>
      <dc:creator>Ruqiu_C_Intel</dc:creator>
      <dc:date>2022-09-16T06:04:33Z</dc:date>
    </item>
    <item>
      <title>Re:Integer arithmetic overflow</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1415174#M28110</link>
      <description>&lt;P&gt;The founding will put into our backlog. For now, this issue is closing and we will no longer respond to this thread.&amp;nbsp;If you require additional assistance from Intel, please start a new thread.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any further interaction in this thread will be considered community only.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Ruqiu&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Sep 2022 06:15:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Integer-arithmetic-overflow/m-p/1415174#M28110</guid>
      <dc:creator>Ruqiu_C_Intel</dc:creator>
      <dc:date>2022-09-16T06:15:01Z</dc:date>
    </item>
  </channel>
</rss>

