-
Notifications
You must be signed in to change notification settings - Fork 89
Graceful exit for transpose/adjoint on size 0 arrays #613
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
Conversation
|
Your PR no longer requires formatting changes. Thank you for your contribution! |
|
Isn't a |
|
Mostly to follow the style above in the function |
|
Still, doesn't seem very legible to me. I'd prefer a simple |
|
Is there a good way to test this only on CUDA? I think size 0 GPU arrays are not allowed on Metal/oneAPI? |
|
Size 0 arrays should always work, or at least we promise they do (so we avoid hitting the allocator when unsupported by the underlying toolkit); this is a bug in Metal.jl. |
31d4914 to
98654bb
Compare
|
Somehow I forgot to merge this? Going to do an update to make sure it still passes then set auto merge |
Right now if you try to take the
transpose!/adjoint!of an array with one or more dimensions of size 0, you'll get an integer division error in the launch configuration step. Not ideal.