-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strided Iterators and 'Skip' Iterators #706
Comments
I think it only exists as an example: https://github.com/thrust/thrust/blob/master/examples/strided_range.cu |
@henryiii thanks, I wonder why it hasn't been formally added in to thrust. Any additional thoughts regarding the 'padding' problem? |
This falls into the broader category of "multi-dimensional" support, I think, although a skip iterator could be useful for a linear sequence. We don't have a firm design for what we're going to do in this space. But, I imagine we'll eventually want a family of strided iterators. Note, however, that traditionally such iterators have all sorts of performance problems. SEE ALSO: https://www.youtube.com/watch?v=EVGenON6p9g |
@brycelelbach @allisonvacanti there have been several times where I've wanted something very simple like this for linear sequences. I don't think we need a full on md-span or multi-dimensional iterator for something this simple. Similarly, I've wanted a I imagine these would look something like this:
|
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1899r0.pdf Equivalent for ranges. |
Fix radix sort / MSVC 2017
Is there anything equivalent in Thrust that corresponds to the
strided_iterator
found in boost compute? On the same topic of operating on specific elements of a buffer, is there a way to operator on 'padded' objects? Note, I also have this same question posted in boost compute For example, take the row-wise padded matrix:So the internal flat buffer would be
As an example, how could I use
sort
on just the 'non-padded' elements?Likewise, the column wise may also be padded (less common but might as well include here)
The text was updated successfully, but these errors were encountered: