It would be really great to get the DCompute codegen options into the LDC property page. I believe one necessary option is -mdcompute-targets=, and I'm not sure if there are other related build options that should also be exposed (there's not great resource available on using DCompute).
Ideally, it would be really good to see DCompute as a 1st-class feature when using LDC with VisualD, I think to execute that, there might also be some detail to make sure the compute object files find their way to the linker correctly.
Users specify a set of compute targets, and I believe each one emits a separate object file... they should all be linked.
Eg: -mdcompute-targets=ocl-210,cuda-350 would emit the normal compiled object, and in addition, OpenCL2.1 and CUDA3.5 objects.
I've asked Nick about an option to embed the kernels into the main object file with appropriately mangled symbol names, but I don't think that exists yet.
turkeyman reported this on 2019-05-31T20:23:00Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=19929
Description
It would be really great to get the DCompute codegen options into the LDC property page. I believe one necessary option is
-mdcompute-targets=, and I'm not sure if there are other related build options that should also be exposed (there's not great resource available on using DCompute).Ideally, it would be really good to see DCompute as a 1st-class feature when using LDC with VisualD, I think to execute that, there might also be some detail to make sure the compute object files find their way to the linker correctly. Users specify a set of compute targets, and I believe each one emits a separate object file... they should all be linked. Eg:
-mdcompute-targets=ocl-210,cuda-350would emit the normal compiled object, and in addition, OpenCL2.1 and CUDA3.5 objects.I've asked Nick about an option to embed the kernels into the main object file with appropriately mangled symbol names, but I don't think that exists yet.