<?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:Using buffer iteration end in Intel® oneAPI DPC++/C++ Compiler</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1452996#M2765</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks for posting in Intel communities.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Every parallel algorithm in Extension API has fixed default parameters and we cannot change syntax.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;For example please refer to below syntax of reduce_by_segment:&lt;/P&gt;&lt;P&gt;reduce_by_segment(Policy&amp;amp;&amp;amp; policy, InputIterator1 first1, InputIterator1 last1, InputIterator2 first2,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;OutputIterator1 result1, OutputIterator2 result2, BinaryPred binary_pred, BinaryOperator binary_op)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;As each reduction is computed with a reduction operation for a subsequence of values, which are determined by keys.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&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;Noorjahan.&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 03 Feb 2023 09:42:43 GMT</pubDate>
    <dc:creator>NoorjahanSk_Intel</dc:creator>
    <dc:date>2023-02-03T09:42:43Z</dc:date>
    <item>
      <title>Using buffer iteration end</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1452235#M2760</link>
      <description>&lt;P&gt;Looking at the oneAPI examples on jupyter notebook, when creating iterations buffers, I didn`t understand why only a end for buf_in was created and not for the others as well.&lt;/P&gt;
&lt;P&gt;auto keys_begin = oneapi::dpl::begin(buf_in);&lt;BR /&gt;auto keys_end = oneapi::dpl::end(buf_in);&lt;BR /&gt;auto vals_begin = oneapi::dpl::begin(buf_seq);&lt;BR /&gt;auto result_key_begin = oneapi::dpl::begin(buf_out_keys);&lt;BR /&gt;auto result_vals_begin = oneapi::dpl::begin(buf_out_vals);&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;(It is a code from the&amp;nbsp;oneDPL - Extension APIs.ipynb)&lt;/P&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;</description>
      <pubDate>Wed, 01 Feb 2023 16:05:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1452235#M2760</guid>
      <dc:creator>Renan1</dc:creator>
      <dc:date>2023-02-01T16:05:58Z</dc:date>
    </item>
    <item>
      <title>Re:Using buffer iteration end</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1452996#M2765</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks for posting in Intel communities.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Every parallel algorithm in Extension API has fixed default parameters and we cannot change syntax.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;For example please refer to below syntax of reduce_by_segment:&lt;/P&gt;&lt;P&gt;reduce_by_segment(Policy&amp;amp;&amp;amp; policy, InputIterator1 first1, InputIterator1 last1, InputIterator2 first2,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;OutputIterator1 result1, OutputIterator2 result2, BinaryPred binary_pred, BinaryOperator binary_op)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;As each reduction is computed with a reduction operation for a subsequence of values, which are determined by keys.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&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;Noorjahan.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 03 Feb 2023 09:42:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1452996#M2765</guid>
      <dc:creator>NoorjahanSk_Intel</dc:creator>
      <dc:date>2023-02-03T09:42:43Z</dc:date>
    </item>
    <item>
      <title>Re:Using buffer iteration end</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1455208#M2790</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 &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Noorjahan.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Feb 2023 06:20:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1455208#M2790</guid>
      <dc:creator>NoorjahanSk_Intel</dc:creator>
      <dc:date>2023-02-10T06:20:36Z</dc:date>
    </item>
    <item>
      <title>Re:Using buffer iteration end</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1457407#M2830</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.&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>Mon, 20 Feb 2023 05:28:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/Using-buffer-iteration-end/m-p/1457407#M2830</guid>
      <dc:creator>SeshaP_Intel</dc:creator>
      <dc:date>2023-02-20T05:28:09Z</dc:date>
    </item>
  </channel>
</rss>

