This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [libstdc++-v3 parallel mode] lack of __gnu_parallel::copy and inconvenience of transform overload
- From: Paolo Carlini <paolo dot carlini at oracle dot com>
- To: Bernard Hugueney <bernard at bernard-hugueney dot org>
- Cc: libstdc++ at gcc dot gnu dot org, Johannes Singler <singler at ira dot uka dot de>
- Date: Tue, 17 Mar 2009 18:14:22 +0100
- Subject: Re: [libstdc++-v3 parallel mode] lack of __gnu_parallel::copy and inconvenience of transform overload
- References: <eed7a5d30903170901h13a1ce74s52c865f6ec56b78@mail.gmail.com> <eed7a5d30903170933v7eee3432m4141f9092cc769d7@mail.gmail.com>
Hi,
> While using __gnu_parallel, I could not guess nor find the reason not
> to have a __gnu_parallel::copy, which should be embarrassingly
> parallel for random iterators. I settled for __gnu_parallel::transform
> using an identity Op, which brings me to my second question/remark :
> given that the overload of std:transform (for 1 or 2 input sequences)
> interferes with the additional optional parameter for __gnu_parallel::
> algorithms, would it be possible to provide
> __gnu_parallel::transform1(...,__gnu_parallel::_Parallelism ) and
> __gnu_parallel::transform2(...,__gnu_parallel::_Parallelism ) to allow
> an easy selection of the parallelism of the transform algorithms over
> 1 and 2 input sequences ?
>
Johannes, what do you think? Are you already aware of this kind of
request? Should we add it to libstdc++/38875?
Paolo.