<?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:My DPC++ program can't run on an intel ATS-P GPU. why? in Intel® oneAPI DPC++/C++ Compiler</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1380683#M2095</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are working on this internally and will get back to you soon.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Hemanth&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 29 Apr 2022 10:12:07 GMT</pubDate>
    <dc:creator>HemanthCH_Intel</dc:creator>
    <dc:date>2022-04-29T10:12:07Z</dc:date>
    <item>
      <title>My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1379416#M2075</link>
      <description>&lt;P&gt;The DPC++ code is very simple, just have a local array ,set the value of array be 0 and barrier mem.&lt;/P&gt;
&lt;PRE class="lang-cpp s-code-block"&gt;&lt;CODE class="hljs language-cpp"&gt; &lt;SPAN class="hljs-meta"&gt;#&lt;SPAN class="hljs-keyword"&gt;include&lt;/SPAN&gt; &lt;SPAN class="hljs-string"&gt;&amp;lt;CL/sycl.hpp&amp;gt;&lt;/SPAN&gt;&lt;/SPAN&gt;
 &lt;SPAN class="hljs-keyword"&gt;using&lt;/SPAN&gt; &lt;SPAN class="hljs-keyword"&gt;namespace&lt;/SPAN&gt; sycl;
 &lt;SPAN class="hljs-meta"&gt;#&lt;SPAN class="hljs-keyword"&gt;define&lt;/SPAN&gt; WRAP_SIZE 32&lt;/SPAN&gt;
 &lt;SPAN class="hljs-function"&gt;&lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; &lt;SPAN class="hljs-title"&gt;main&lt;/SPAN&gt;&lt;SPAN class="hljs-params"&gt;()&lt;/SPAN&gt;&lt;/SPAN&gt;{
    sycl::gpu_selector selector;
    &lt;SPAN class="hljs-function"&gt;queue &lt;SPAN class="hljs-title"&gt;exec_queue&lt;/SPAN&gt;&lt;SPAN class="hljs-params"&gt;(selector)&lt;/SPAN&gt;&lt;/SPAN&gt;;
    &lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; num_blocks=&lt;SPAN class="hljs-number"&gt;128&lt;/SPAN&gt;;
    &lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; num_threads=&lt;SPAN class="hljs-number"&gt;256&lt;/SPAN&gt;;
    &lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; casBeg=&lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;;
    &lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; casEnd=&lt;SPAN class="hljs-number"&gt;2&lt;/SPAN&gt;;
    exec_queue.&lt;SPAN class="hljs-built_in"&gt;submit&lt;/SPAN&gt;([&amp;amp;](sycl::handler&amp;amp; cgh)
    {
        sycl::stream out{ &lt;SPAN class="hljs-number"&gt;4096&lt;/SPAN&gt;, &lt;SPAN class="hljs-number"&gt;128&lt;/SPAN&gt;, cgh };
        &lt;SPAN class="hljs-keyword"&gt;auto&lt;/SPAN&gt; sharedmem = sycl::&lt;SPAN class="hljs-built_in"&gt;accessor&lt;/SPAN&gt;&amp;lt;&lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt;, &lt;SPAN class="hljs-number"&gt;1&lt;/SPAN&gt;, sycl::access_mode::read_write, sycl::access::target::local&amp;gt;(&lt;SPAN class="hljs-number"&gt;11&lt;/SPAN&gt;, cgh);
        cgh.&lt;SPAN class="hljs-built_in"&gt;parallel_for&lt;/SPAN&gt;(
            sycl::&lt;SPAN class="hljs-built_in"&gt;nd_range&lt;/SPAN&gt;&amp;lt;&lt;SPAN class="hljs-number"&gt;1&lt;/SPAN&gt;&amp;gt;(num_blocks * num_threads, num_threads),
            [=](sycl::nd_item&amp;lt;&lt;SPAN class="hljs-number"&gt;1&lt;/SPAN&gt;&amp;gt; item_ct1) [[intel::&lt;SPAN class="hljs-built_in"&gt;reqd_sub_group_size&lt;/SPAN&gt;(WRAP_SIZE)]] {
                &lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; blkId = item_ct1.&lt;SPAN class="hljs-built_in"&gt;get_group&lt;/SPAN&gt;(&lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;);
                &lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; tid = item_ct1.&lt;SPAN class="hljs-built_in"&gt;get_local_id&lt;/SPAN&gt;(&lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;);
                &lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; stride = item_ct1.&lt;SPAN class="hljs-built_in"&gt;get_local_range&lt;/SPAN&gt;().&lt;SPAN class="hljs-built_in"&gt;get&lt;/SPAN&gt;(&lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;);
                        out&amp;lt;&amp;lt;&lt;SPAN class="hljs-string"&gt;"inter\n"&lt;/SPAN&gt;;
                &lt;SPAN class="hljs-keyword"&gt;if&lt;/SPAN&gt; (tid == &lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;)
                    &lt;SPAN class="hljs-keyword"&gt;for&lt;/SPAN&gt; (&lt;SPAN class="hljs-type"&gt;int&lt;/SPAN&gt; i = &lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;; i &amp;lt; &lt;SPAN class="hljs-number"&gt;11&lt;/SPAN&gt;; ++i)
                        sharedmem[i] = &lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;;
                item_ct1.&lt;SPAN class="hljs-built_in"&gt;barrier&lt;/SPAN&gt;(sycl::access::fence_space::local_space);
            });
    }).&lt;SPAN class="hljs-built_in"&gt;wait&lt;/SPAN&gt;();
    &lt;SPAN class="hljs-keyword"&gt;return&lt;/SPAN&gt; &lt;SPAN class="hljs-number"&gt;0&lt;/SPAN&gt;;
 }
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;The build command is&lt;/P&gt;
&lt;PRE class="lang-sh s-code-block"&gt;&lt;CODE class="hljs language-bash"&gt;dpcpp -DMKL_ILP64 -lmkl_sycl -lmkl_intel_ilp64 -lmkl_tbb_thread -lmkl_core -pthread -std=c++17 -O0 -o &amp;lt;project_name&amp;gt; &amp;lt;code_name&amp;gt;.cpp
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;Compiled program can work ok on the P690 GPU, but not work on the NDK intel ATS-P GPU. Why? How to Fix it?Thx&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 05:53:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1379416#M2075</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-04-25T05:53:47Z</dc:date>
    </item>
    <item>
      <title>Re: My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1379773#M2079</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for posting in Intel Communities.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you please provide the DPC++ version and OS details, So that we can reproduce the issue from our end?&lt;/P&gt;
&lt;P&gt;Use the below command to find the DPC++ version:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;source /opt/intel/oneapi/setvars.sh
dpcpp --version

&lt;/LI-CODE&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;Hemanth&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Apr 2022 10:38:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1379773#M2079</guid>
      <dc:creator>HemanthCH_Intel</dc:creator>
      <dc:date>2022-04-26T10:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1380259#M2090</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I am running under NDA devcloud. I do not know the os detail. The result of&amp;nbsp; uname -a is&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="bash"&gt;Linux s013-n002 5.10.54+prerelease2606 #1 SMP Fri Jan 7 14:21:53 PST 2022 x86_64 x86_64 x86_64 GNU/Linux&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The result of /proc/version is&lt;/P&gt;
&lt;LI-CODE lang="bash"&gt;Linux version 5.10.54+prerelease2606 (ubit@fm6pudocker153) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP Fri Jan 7 14:21:53 PST 2022&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The result of dpcpp --version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="bash"&gt;Intel(R) oneAPI DPC++/C++ Compiler 2022.0.0 (2022.0.0.20211123)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /nda/development-tools/versions/oneapi/2022.1.0.nda/oneapi/compiler/2022.0.1-prerelease/linux/bin-llvm&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 00:27:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1380259#M2090</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-04-28T00:27:00Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1380683#M2095</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are working on this internally and will get back to you soon.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Hemanth&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Apr 2022 10:12:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1380683#M2095</guid>
      <dc:creator>HemanthCH_Intel</dc:creator>
      <dc:date>2022-04-29T10:12:07Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1381694#M2105</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I don't see any MKL calls in the code.  Please help me understand why you have used MKL libraries in the build command? It works perfect without the MKL flags.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Subarna&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 04 May 2022 10:22:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1381694#M2105</guid>
      <dc:creator>Subarnarek_G_Intel</dc:creator>
      <dc:date>2022-05-04T10:22:06Z</dc:date>
    </item>
    <item>
      <title>Re: Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1381877#M2108</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt; Subarna&lt;/SPAN&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Employee"&gt;&lt;SPAN class="lia-link-navigation lia-page-link lia-link-disabled lia-user-name-link"&gt;&lt;SPAN class="login-bold"&gt;,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I have a project use some mkl functions(e.g. gemm and LU functions).But the project can not run correct in ATS-P card. So, I debug it and found the problem when add mkl flags. To simply describe the problem, I abstracted the simplest code.&amp;nbsp;And, it is very confusing that if you add the MKL flags, the program will not run correctly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 00:36:08 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1381877#M2108</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-05-05T00:36:08Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1383778#M2132</link>
      <description>&lt;P&gt;Hi Li,&lt;/P&gt;&lt;P&gt;This is not a generic issue. Refer to this code for example &lt;A href="https://github.com/oneapi-src/oneAPI-samples/blob/master/Libraries/oneMKL/matrix_mul_mkl" target="_blank"&gt;https://github.com/oneapi-src/oneAPI-samples/blob/master/Libraries/oneMKL/matrix_mul_mkl&lt;/A&gt;. It works perfectly fine on ATS. What is the error that you got? Can you refer to the make file to start the build with. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Subarna&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 May 2022 11:18:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1383778#M2132</guid>
      <dc:creator>Subarnarek_G_Intel</dc:creator>
      <dc:date>2022-05-12T11:18:12Z</dc:date>
    </item>
    <item>
      <title>Re: Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1384013#M2141</link>
      <description>&lt;P&gt;Hi Subarna&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thank you for your answer. First of all, based on your hint, I ran the usm example of oneMKL gemm (Devcloud path is ~/Intel_oneAPI_MKL_Training/00_GEMM/.Script is run_gemm_usm.sh). it doesn't work on ATS-P(NDK devcloud). The error message is CL_INVALID_DEVICE. Second, I added my code (paste below) below the sample code you gave. It still doesn't work on ATS-P with a compilation optimization level of O0.Usually, we need to use O0 optimization to debug the code.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;My code snippet is:&lt;/SPAN&gt;&lt;/P&gt;
&lt;LI-CODE lang="cpp"&gt;    queue.submit([&amp;amp;](sycl::handler&amp;amp; cgh)
    {
        sycl::stream out{ 4096, 128, cgh };
        cgh.parallel_for(
            sycl::nd_range&amp;lt;1&amp;gt;(num_blocks * num_threads, num_threads),
            [=](sycl::nd_item&amp;lt;1&amp;gt; item_ct1) [[intel::reqd_sub_group_size(32)]] {
                int stride = item_ct1.get_local_range().get(0);
                item_ct1.barrier(sycl::access::fence_space::local_space);
            });
    }).wait();&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;Regards,&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;Dack&lt;/P&gt;</description>
      <pubDate>Fri, 13 May 2022 04:03:25 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1384013#M2141</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-05-13T04:03:25Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388513#M2224</link>
      <description>&lt;P&gt;Hi Li,&lt;/P&gt;&lt;P&gt;&lt;A href="https://jupyter.oneapi.devcloud.intel.com/user/u29878/lab/tree/Intel_oneAPI_MKL_Training/00_GEMM/02_GEMM_DPCPP_USM.ipynb" target="_blank"&gt;https://jupyter.oneapi.devcloud.intel.com/user/u29878/lab/tree/Intel_oneAPI_MKL_Training/00_GEMM/02_GEMM_DPCPP_USM.ipynb&lt;/A&gt; works fine for me. I think you didn't follow the instructions of uncommenting certain lines of code.&lt;/P&gt;&lt;P&gt;"Uncomment _one_ of the following three lines to select a device." - look for this line.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Subarna&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 30 May 2022 06:54:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388513#M2224</guid>
      <dc:creator>Subarnarek_G_Intel</dc:creator>
      <dc:date>2022-05-30T06:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388522#M2225</link>
      <description>&lt;P&gt;Hi &lt;SPAN&gt;Subarna&lt;/SPAN&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for your answer, the first question was an oversight on my part. Regarding the second question, how is it explained?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;Regards,&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;Dack&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2022 07:21:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388522#M2225</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-05-30T07:21:55Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388770#M2227</link>
      <description>&lt;P&gt;Hi Li,&lt;/P&gt;&lt;P&gt;I am getting a bit confused now? What are you trying to achieve from the thread? Is it an issue with MKL flags not getting used properly or is it that the code snippet with barrier functions that you put inside the MKL sample doesn't work? If that is the issue then I need to understand properly where have you put this code snippet in that code? &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 31 May 2022 06:01:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388770#M2227</guid>
      <dc:creator>Subarnarek_G_Intel</dc:creator>
      <dc:date>2022-05-31T06:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388782#M2228</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Subarna,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Code&lt;/SPAN&gt;&lt;/P&gt;
&lt;LI-CODE lang="cpp"&gt;#include &amp;lt;iostream&amp;gt;
#include &amp;lt;vector&amp;gt;
#include &amp;lt;CL/sycl.hpp&amp;gt;          //# sycl namespace
#include "oneapi/mkl/blas.hpp"  //# oneMKL DPC++ interface for BLAS functions

//# The following project performs matrix multiplication using oneMKL / DPC++ with buffers.
//# We will execute the simple operation A * B = C
//# The matrix B is set equal to the identity matrix such that A * B = A * I
//# After performing the computation, we will verify A * I = C -&amp;gt; A = C

namespace mkl = oneapi::mkl;  //# shorten mkl namespace

int main() {

    //# dimensions
    int m = 3, n = 3, k = 3;
    //# leading dimensions
    int ldA = 3, ldB = 3, ldC = 3;
    //# scalar multipliers
    double alpha = 1.0, beta = 1.0;
    //# transpose status of matrices
    mkl::transpose transA = mkl::transpose::nontrans;
    mkl::transpose transB = mkl::transpose::nontrans;
    //# matrix data
    std::vector&amp;lt;double&amp;gt; A = {1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0};
    std::vector&amp;lt;double&amp;gt; B = {1.0, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0};
    std::vector&amp;lt;double&amp;gt; C = {0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0};

    //### Step 1 - Observe the definition of an asynchronous exception handler.
    //# This function object will later be supplied to the queue.
    //# It is designed to handle errors thrown while device code executes.
    auto async_handler = [](sycl::exception_list exceptions) {
        for (std::exception_ptr const &amp;amp;e : exceptions) {
            try {
                std::rethrow_exception(e);
            }
            catch (sycl::exception const &amp;amp;e) {
                std::cout &amp;lt;&amp;lt; "Caught asynchronous SYCL exception: " &amp;lt;&amp;lt; e.what() &amp;lt;&amp;lt; std::endl;
            }
        }
    };

    //### Step 2 - Create a device object.
    //# Device selectors are used to specify the type of a device.
    //# Uncomment _one_ of the following three lines to select a device.
    // sycl::device device = sycl::device(sycl::default_selector());  //# default_selector returns a device based on a performance heuristic
    // sycl::device device = sycl::device(sycl::cpu_selector());      //# cpu_selector returns a cpu device
    sycl::device device = sycl::device(sycl::gpu_selector());      //# gpu_selector returns a gpu device
    std::cout &amp;lt;&amp;lt; "Device: " &amp;lt;&amp;lt; device.get_info&amp;lt;sycl::info::device::name&amp;gt;() &amp;lt;&amp;lt; std::endl;

    //### Step 3 - Create a queue object.
    //# A queue accepts a single device, and optionally, an exception handler.
    //# Uncomment the following line to initialize a queue with our device and handler.
    sycl::queue queue(device, async_handler);

    //### Step 4 - Create buffers to hold our matrix data.
    //# Buffer objects can be constructed given a container
    //# Observe the creation of buffers for matrices A and B.
    //# Try and create a third buffer for matrix C called C_buffer.
    //# The solution is shown in the hidden cell below.
    sycl::buffer A_buffer(A);
    sycl::buffer B_buffer(B);
    /* define C_buffer here */
    sycl::buffer C_buffer(C);

    //### Step 5 - Execute gemm operation.
    //# Here, we need only pass in our queue and other familiar matrix multiplication parameters.
    //# This includes the dimensions and data buffers for matrices A, B, and C.
    mkl::blas::gemm(queue, transA, transB, m, n, k, alpha, A_buffer, ldA, B_buffer, ldB, beta, C_buffer, ldC);

    //# we cannot explicitly transfer memory to/from the device when using buffers
    //# that is why we must use this operation to ensure result data is returned to the host
    queue.wait_and_throw();  //# block until operation completes, throw any errors

    //### Step 6 - Observe creation of accessors to retrieve data from A_buffer and C_buffer.
    sycl::host_accessor A_acc(A_buffer, sycl::read_only);
    sycl::host_accessor C_acc(C_buffer, sycl::read_only);

    int status = 0;

    // verify C matrix using accessor to observe values held in C_buffer
    std::cout &amp;lt;&amp;lt; std::endl;
    std::cout &amp;lt;&amp;lt; "C = " &amp;lt;&amp;lt; std::endl;
    for (int i = 0; i &amp;lt; m; ++i) {
        for (int j = 0; j &amp;lt; n; ++j) {
            if (A_acc[i*m+j] != C_acc[i*m+j]) status = 1;
            std::cout &amp;lt;&amp;lt; C_acc[i*m+j] &amp;lt;&amp;lt; " ";
        }
        std::cout &amp;lt;&amp;lt; std::endl;
    }
    std::cout &amp;lt;&amp;lt; std::endl;
        int num_blocks=128;
    int num_threads=256;
    queue.submit([&amp;amp;](sycl::handler&amp;amp; cgh)
    {
        sycl::stream out{ 4096, 128, cgh };
//         auto sharedmem = sycl::accessor&amp;lt;int, 1, sycl::access_mode::read_write, sycl::access::target::local&amp;gt;(11, cgh);
        cgh.parallel_for(
            sycl::nd_range&amp;lt;1&amp;gt;(num_blocks * num_threads, num_threads),
            [=](sycl::nd_item&amp;lt;1&amp;gt; item_ct1) [[intel::reqd_sub_group_size(32)]] {
                out&amp;lt;&amp;lt;"inter\n";
                int warpSize = item_ct1.get_sub_group().get_local_range()[0];
                item_ct1.barrier(sycl::access::fence_space::local_space);
            });
    }).wait();
    status == 0 ? std::cout &amp;lt;&amp;lt; "Verified: A = C" &amp;lt;&amp;lt; std::endl : std::cout &amp;lt;&amp;lt; "Failed: A != C" &amp;lt;&amp;lt; std::endl;
    return status;
}
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;Compile&lt;/P&gt;
&lt;LI-CODE lang="bash"&gt;dpcpp lab/dpcpp_gemm_buffers.cpp -fsycl-device-code-split=per_kernel -DMKL_ILP64 -I$MKLROOT/include -L$MKLROOT/lib/intel64 -lmkl_sycl -lmkl_intel_ilp64 -lmkl_sequential -lmkl_core -lsycl -lOpenCL -lpthread -lm -ldl -O0&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Result:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PcDack1_0-1653979197943.png" style="width: 999px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/30046i5968C0BA84B704C6/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="PcDack1_0-1653979197943.png" alt="PcDack1_0-1653979197943.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Question:&lt;/P&gt;
&lt;P&gt;There is printing in kernal, but actually there is no printed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 May 2022 06:43:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388782#M2228</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-05-31T06:43:36Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388799#M2229</link>
      <description>&lt;P&gt;Hi Li,&lt;/P&gt;&lt;P&gt;Can you explain what you meant by "There is printing in kernel, but actually there is no printed."&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Subarna&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 31 May 2022 07:22:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388799#M2229</guid>
      <dc:creator>Subarnarek_G_Intel</dc:creator>
      <dc:date>2022-05-31T07:22:40Z</dc:date>
    </item>
    <item>
      <title>Re: Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388810#M2230</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;SPAN&gt;Subarna,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PcDack1_0-1653982116445.png" style="width: 999px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/30048i75445865C7C74DF6/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="PcDack1_0-1653982116445.png" alt="PcDack1_0-1653982116445.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The correct result should be&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;Device:Intel Graphics [0x020a]

C=
1 2 3
4 5 6
7 8 9

inter
inter
...

verified:A=C&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I don't see the "inter" being printed out.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PcDack1_2-1653982355777.png" style="width: 999px;"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/30050iAD5A16B5ACF0B6C1/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="PcDack1_2-1653982355777.png" alt="PcDack1_2-1653982355777.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Tue, 31 May 2022 07:34:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1388810#M2230</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-05-31T07:34:43Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1389231#M2239</link>
      <description>&lt;P&gt;Hi Li,&lt;/P&gt;&lt;P&gt;It gets displayed for me.&lt;/P&gt;&lt;P&gt;## u29878 is compiling oneMKL_introduction Module0 -- gemm with buffers - 1 of 3 dpcpp_gemm_buffers.cpp&lt;/P&gt;&lt;P&gt;Device: Intel(R) UHD Graphics P630 [0x3e96]&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;C = &lt;/P&gt;&lt;P&gt;1 2 3 &lt;/P&gt;&lt;P&gt;4 5 6 &lt;/P&gt;&lt;P&gt;7 8 9 &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;inter&lt;/P&gt;&lt;P&gt;....&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Jun 2022 11:00:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1389231#M2239</guid>
      <dc:creator>Subarnarek_G_Intel</dc:creator>
      <dc:date>2022-06-01T11:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1389386#M2242</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Subarna,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Thx, All my problems are on the ATS-P graphics card(on devcloud). You have only tested it on the P630 graphics card.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 22:55:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1389386#M2242</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-06-01T22:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1390394#M2256</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;First of all, I apologize for not describing the problem precisely. In order to make the problem more clear, my team and I, after repeated testing, found that the problem can be described in a simpler way(related to sycl::stream). I created a new &lt;A href="https://community.intel.com/t5/Intel-oneAPI-Data-Parallel-C/Stuck-on-ATS-P-GPUs/m-p/1390392" target="_self"&gt;post&lt;/A&gt; to describe the problem. The current post will no longer be maintained.&lt;/P&gt;
&lt;P&gt;Thx all.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks &amp;amp; Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Dack&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2022 00:32:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1390394#M2256</guid>
      <dc:creator>PcDack1</dc:creator>
      <dc:date>2022-06-07T00:32:03Z</dc:date>
    </item>
    <item>
      <title>Re:My DPC++ program can't run on an intel ATS-P GPU. why?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1390523#M2259</link>
      <description>&lt;P&gt;&lt;I style="font-family: Calibri, sans-serif; font-size: 11pt;"&gt;This issue has been resolved 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;Any further interaction in this thread will be considered community only&lt;/I&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Jun 2022 07:29:57 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/My-DPC-program-can-t-run-on-an-intel-ATS-P-GPU-why/m-p/1390523#M2259</guid>
      <dc:creator>Subarnarek_G_Intel</dc:creator>
      <dc:date>2022-06-07T07:29:57Z</dc:date>
    </item>
  </channel>
</rss>

