-
Notifications
You must be signed in to change notification settings - Fork 27
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
ndslice integration #14
Comments
Definitely.
|
Do you mean mir.ndslice should be marked? |
yes. I think it would be good to have a module (probably in dcompute) that imports all the relevant dcompute symbols from |
@thewilsonator Why not to allow any generic code to be instantiated in a marked module? |
?? Not sure what you mean. Any modules, regardless of its |
I mean that I do not understand why ndslice should be marked if it is completely generic. If we call a generic function from kernel function it can be automatically determinated that generic should be compiled for kernel |
Actually that might work. I'm not quite sure how template instances end up in a given module's symbol table, but if it does because it is referenced by that module, then the code would suggest that that would work. We would still need |
Can we use library @nothrow @nogc generic code in kernels. For example
Slice!(Contiguous, [1], GlobalPointer!T)
and ndslice topology?The text was updated successfully, but these errors were encountered: