Skip to content

Add reverse! and reverse#102

Open
shreyas-omkar wants to merge 1 commit into
JuliaGPU:mainfrom
shreyas-omkar:sh/reverse-clean
Open

Add reverse! and reverse#102
shreyas-omkar wants to merge 1 commit into
JuliaGPU:mainfrom
shreyas-omkar:sh/reverse-clean

Conversation

@shreyas-omkar

Copy link
Copy Markdown
Member

Reverse a vector in-place by swapping symmetric pairs, so only length ÷ 2 threads are launched and no temporary array is allocated. Odd-length arrays keep their middle element in place.

Also provides a two-argument reverse!(dst, src) writing into a caller-supplied buffer, and an allocating reverse(v).

Measured against CUDA.jl and torch.flip on an RTX 3060 and an RTX 5080: at large n all three converge on device-to-device copy bandwidth (within 1-2% of copyto!, 92% of peak on the 3060), since reverse reads n and writes n with no reuse to exploit. Below 100M elements this is 2.4-2.8x faster than torch.flip, which carries a flat ~70us dispatch floor.

Reverse a vector in-place by swapping symmetric pairs, so only length ÷ 2
threads are launched and no temporary array is allocated. Odd-length arrays
keep their middle element in place.

Also provides a two-argument reverse!(dst, src) writing into a caller-supplied
buffer, and an allocating reverse(v).

Measured against CUDA.jl and torch.flip on an RTX 3060 and an RTX 5080: at
large n all three converge on device-to-device copy bandwidth (within 1-2% of
copyto!, 92% of peak on the 3060), since reverse reads n and writes n with no
reuse to exploit. Below 100M elements this is 2.4-2.8x faster than torch.flip,
which carries a flat ~70us dispatch floor.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@shreyas-omkar
shreyas-omkar marked this pull request as ready for review July 22, 2026 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant