Skip to content

[0.9] Unified memory allocations #632

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

Merged
merged 14 commits into from
Jul 22, 2025
Merged

Conversation

christiangnrd
Copy link
Member

See #630

Feedback from #630 has been addressed. When not implemented in the backend, no kwarg or unified=false just work, while unified=true will fail unless implemented.

Copy link
Contributor

github-actions bot commented Jul 21, 2025

Your PR no longer requires formatting changes. Thank you for your contribution!

@christiangnrd
Copy link
Member Author

Errors unrelated?

Copy link
Member

@vchuravy vchuravy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you implement the cpu.jl changes as well. The CPU backend does support unified by default.

@vchuravy
Copy link
Member

4c0c6da

@vchuravy vchuravy changed the title [0.9] Proof-of-concept unified memory allocations [0.9] Unified memory allocations Jul 22, 2025
@christiangnrd
Copy link
Member Author

Errors unrelated should be gtg.

@vchuravy
Copy link
Member

The docs error is introduced. You need to add supports_unified to the API docs.

@christiangnrd
Copy link
Member Author

Because of my inclusion of a reference to it in another docstring. Fixed.

@vchuravy vchuravy merged commit 1a580ab into JuliaGPU:release-0.9 Jul 22, 2025
32 of 36 checks passed
@christiangnrd christiangnrd deleted the uni0.9 branch July 22, 2025 17:24
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.

2 participants