-
Notifications
You must be signed in to change notification settings - Fork 63
Projections do not play well with GPUCompiler #429
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
Comments
I think we should do something like the first fix. The whole constructor function can be dispatch not branching, without loss, it just happened to get written that way: Edit -- like this commit, maybe: 7e5ae8e The second seems trickier, it's avoiding this if
It's possible that we should insist that every array projector has It's also possible that we should mark the two cases in some way easier to dispatch off of? One iteration of this thing had (It's also possible that we should |
ChainRulesCore v1.3.1, latest, has the above branch-free construction of projectors, but still has If I try the linked gist, on latest everything (CUDA v3.4.2) I get a warning on the first run, but subsequent runs are find. Can you confirm what you see, and whether you think there are sill problems here?
PR #430 removes the |
Here's an example that does not play well with
GPUCompiler
: https://gist.github.com/pabloferz/1390d85383e3243015be7ad5b162bcc4A possible, but probably incomplete fix discussed with @mcabbott, is having the following specializations:
The text was updated successfully, but these errors were encountered: