Intel® oneAPI DPC++/C++ Compiler
Talk to fellow users of Intel® oneAPI DPC++/C++ Compiler and companion tools like Intel® oneAPI DPC++ Library, Intel® DPC++ Compatibility Tool, and Intel® Distribution for GDB*

Using buffer iteration end

Renan1
Employee
879 Views

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.

auto keys_begin = oneapi::dpl::begin(buf_in);
auto keys_end = oneapi::dpl::end(buf_in);
auto vals_begin = oneapi::dpl::begin(buf_seq);
auto result_key_begin = oneapi::dpl::begin(buf_out_keys);
auto result_vals_begin = oneapi::dpl::begin(buf_out_vals);

 

(It is a code from the oneDPL - Extension APIs.ipynb)

 

 

 

0 Kudos
3 Replies
NoorjahanSk_Intel
Moderator
776 Views

Hi,


Thanks for posting in Intel communities.


Every parallel algorithm in Extension API has fixed default parameters and we cannot change syntax.


For example please refer to below syntax of reduce_by_segment:

reduce_by_segment(Policy&& policy, InputIterator1 first1, InputIterator1 last1, InputIterator2 first2,

         OutputIterator1 result1, OutputIterator2 result2, BinaryPred binary_pred, BinaryOperator binary_op)


As each reduction is computed with a reduction operation for a subsequence of values, which are determined by keys.



Thanks & Regards,

Noorjahan.


0 Kudos
NoorjahanSk_Intel
Moderator
756 Views

Hi,


We haven't heard back from you. Could you please provide an update on your issue?


Thanks & Regards,

Noorjahan.


0 Kudos
SeshaP_Intel
Moderator
724 Views

Hi,


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.


Thanks and Regards,

Pendyala Sesha Srinivas


0 Kudos
Reply