Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

consider removing device-to-device copy workaround for absence of nvcc #58

Closed
jaredhoberock opened this issue May 7, 2012 · 1 comment
Closed

consider removing device-to-device copy workaround for absence of nvcc #58

jaredhoberock opened this issue May 7, 2012 · 1 comment
Labels
type: enhancement New feature or request.

Comments

@jaredhoberock
Copy link
Contributor

IIRC we decided to eliminate this WAR because it violates the one-definition rule and there's no way to ensure we get the "good" version when both are present.

[1] http://code.google.com/p/thrust/source/browse/thrust/system/cuda/detail/copy_device_to_device.inl#41

I don't think we should modify that code unless we get a bug report

I'll take a look at this later. I can't say what the right approach is, but I'm concerned about the silent (and hard to diagnose) performance hazard that this introduces.

Forwarded from http://code.google.com/p/thrust/issues/detail?id=449
kshitij12345 pushed a commit to kshitij12345/thrust that referenced this issue Mar 24, 2022
- Fix for Infinite loop in cub::CachingDeviceAllocator::NearestPowerOf
de3b04e 
NVIDIA#58

- Update scan and reduce tuning policies

Former-commit-id: 91c869765ad5dbb1c3846d7ceb5b442d0ddc3130
@alliepiper
Copy link
Collaborator

The copy_device_to_device implementation was rewritten in 2016.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type: enhancement New feature or request.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alliepiper @jaredhoberock