search for: sm_

...n.in_ -rwxr-xr-x 1 root wheel 3418 Aug 10 1994 setupw.in_ -rwxr-xr-x 1 root wheel 212659 Aug 10 1994 states.vs_ -rwxr-xr-x 1 root wheel 4888 Aug 10 1994 uninstal.ex_ -rwxr-xr-x 1 root wheel 131568 Aug 10 1994 visio.ex_ -rwxr-xr-x 1 root wheel 183 Aug 10 1994 visio123.sm_ -rwxr-xr-x 1 root wheel 190 Aug 10 1994 visioami.sm_ -rwxr-xr-x 1 root wheel 458 Aug 10 1994 visioami.sx_ -rwxr-xr-x 1 root wheel 222 Aug 10 1994 visioflw.sm_ -rwxr-xr-x 1 root wheel 263 Aug 10 1994 visiolss.bm_ -rwxr-xr-x 1 root wheel 83 Aug 10 1994 visiols...

...old crufty subarchs you would get with an exclusion flag. We expect that the runtime will match the most appropriate subarch. As is currently done with --cuda-gpu-arch, we expect that the triple for the arch will be implied from the context. That is, if one specifies --target-subarchs="sm_50,gfx702", the software will generate the triples "nvptx64-nvidia-cuda" and "amdgcn--cuda" from the subarchs. Collisions (different archs) for the same subarch are unlikely and indicate a poor choice of subarch names. For example, AMD should never choose sm_ prefix for...

...M 3.9, and I've > written a pass to insert hook functions for certain function calls and > memory accesses. For example, given a CUDA program, say, axpy.cu, I > first compile it with > > clang++ -emit-llvm -c axpy.cu, > > which gives me two bitcode files, axpy.bc and axpy-sm_20.bc. Then I use > opt to load my pass and insert the hook functions to axpy.bc, which works > fine. After inspecting the instrumented axpy.bc, I noticed that the kernel > code was not there; rather, it lived inside axpy-sm_20.bc, so I also load > my pass to instrument axpy-sm_20.bc....

...t hook functions for certain function calls and >>> memory accesses. For example, given a CUDA program, say, axpy.cu, I >>> first compile it with >>> >>> clang++ -emit-llvm -c axpy.cu, >>> >>> which gives me two bitcode files, axpy.bc and axpy-sm_20.bc. Then I use >>> opt to load my pass and insert the hook functions to axpy.bc, which works >>> fine. After inspecting the instrumented axpy.bc, I noticed that the kernel >>> code was not there; rather, it lived inside axpy-sm_20.bc, so I also load >>> my pa...