<?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:Bug in usm_allocator.hpp max in Intel® oneAPI DPC++/C++ Compiler</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1430551#M2644</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 in Intel Communities.&lt;/P&gt;&lt;P&gt;Could you please share the sample reproducer code and steps to reproduce so that we can investigate the issue more from our end?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Pendyala Sesha Srinivas&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 16 Nov 2022 09:42:00 GMT</pubDate>
    <dc:creator>SeshaP_Intel</dc:creator>
    <dc:date>2022-11-16T09:42:00Z</dc:date>
    <item>
      <title>Bug in usm_allocator.hpp max</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1430465#M2643</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi Intel Support,&lt;/P&gt;
&lt;P&gt;In the &lt;SPAN&gt;DPC++ release 2022.2.1, there is a bug.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I believe this should be using std::max instead (&lt;A href="https://en.cppreference.com/w/cpp/algorithm/max" target="_blank"&gt;https://en.cppreference.com/w/cpp/algorithm/max&lt;/A&gt;).&lt;/SPAN&gt;&lt;/P&gt;
&lt;LI-CODE lang="none"&gt;In file included from /opt/intel/oneapi/compiler/2022.2.1/linux/bin-llvm/../include/sycl/CL/sycl/usm.hpp:11:
/opt/intel/oneapi/compiler/2022.2.1/linux/bin-llvm/../include/sycl/CL/sycl/usm/usm_allocator.hpp:119:50: error: use of undeclared identifier 'max'; did you mean 'fmax'?
  constexpr size_t getAlignment() const { return max(alignof(T), Alignment); }
                                                 ^
/usr/include/x86_64-linux-gnu/bits/mathcalls.h:329:14: note: 'fmax' declared here
__MATHCALLX (fmax,, (_Mdouble_ __x, _Mdouble_ __y), (__const__));
             ^
&lt;/LI-CODE&gt;
&lt;P&gt;Can you please fix this?&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;S&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 01:02:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1430465#M2643</guid>
      <dc:creator>s1232</dc:creator>
      <dc:date>2022-11-16T01:02:58Z</dc:date>
    </item>
    <item>
      <title>Re:Bug in usm_allocator.hpp max</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1430551#M2644</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 in Intel Communities.&lt;/P&gt;&lt;P&gt;Could you please share the sample reproducer code and steps to reproduce so that we can investigate the issue more from our end?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Pendyala Sesha Srinivas&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 16 Nov 2022 09:42:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1430551#M2644</guid>
      <dc:creator>SeshaP_Intel</dc:creator>
      <dc:date>2022-11-16T09:42:00Z</dc:date>
    </item>
    <item>
      <title>Re:Bug in usm_allocator.hpp max</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1432793#M2650</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We haven't heard back from you. Could you please provide an update on your issue?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Pendyala Sesha Srinivas&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Nov 2022 10:58:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1432793#M2650</guid>
      <dc:creator>SeshaP_Intel</dc:creator>
      <dc:date>2022-11-24T10:58:10Z</dc:date>
    </item>
    <item>
      <title>Re:Bug in usm_allocator.hpp max</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1434798#M2662</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We have not heard back from you. This thread will no longer be monitored by Intel. If you need further assistance, please post a new question.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Pendyala Sesha Srinivas&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Dec 2022 11:56:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Bug-in-usm-allocator-hpp-max/m-p/1434798#M2662</guid>
      <dc:creator>SeshaP_Intel</dc:creator>
      <dc:date>2022-12-01T11:56:18Z</dc:date>
    </item>
  </channel>
</rss>

