We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I created following structure:
. ├── dcompute-app │ ├── dub.sdl │ ├── dub.selections.json │ └── source │ └── app.d └── dcompute-lib ├── dub.sdl ├── dub.selections.json └── source └── dcomputelibrary ├── foo.d // to prevent issue #61 └── testkernel.d
dcompute-app depends on dcompute-lib.
dcompute-app
dcompute-lib
Under this condition, I run dub run --compiler=ldc2. Then the content of .dub/obj/kernels_cuda210_64.ptx becomes almost empty:
dub run --compiler=ldc2
.dub/obj/kernels_cuda210_64.ptx
.text .file "dcomputeTargetCUDA" .section ".note.GNU-stack","",@progbits
I expected the compiled code of testkernel.d is in it.
testkernel.d
This is because ptx is overwritten at dcompute-app build once successfully created at dcompute-lib's build.
The text was updated successfully, but these errors were encountered:
you will need to use -mdcompute-file-prefix=<prefix> (e.g. -mdcompute-file-prefix=dcompute-lib) in your flags to avoid that.
-mdcompute-file-prefix=<prefix>
-mdcompute-file-prefix=dcompute-lib
Sorry, something went wrong.
What you mean is to add that flag to dcompute-lib project?
The flag propagates to dcompute-app and changes the output file of both project.
It does not solve this problem.
No branches or pull requests
I created following structure:
dcompute-app
depends ondcompute-lib
.Under this condition, I run
dub run --compiler=ldc2
.Then the content of
.dub/obj/kernels_cuda210_64.ptx
becomes almost empty:I expected the compiled code of
testkernel.d
is in it.This is because ptx is overwritten at
dcompute-app
build once successfully created atdcompute-lib
's build.The text was updated successfully, but these errors were encountered: