llnl / llnl/blt

how to pass cuda arch settings to blt_cuda_smoke?

Open
#278 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
296
Forks
66
Avg merge
1h 3m
Merged PRs (30d)
1

Description

Using blt fb5633c (master as of 6/13/19)

I have the following set in a host-config file:

```
set(CUDA_ARCH "sm_60" CACHE STRING "")
set(CMAKE_CUDA_ARCH "sm_60" CACHE STRING "")
set(CUDA_NVCC_FLAGS "-arch=sm_60" CACHE STRING "")
```
None of these propgate to the `blt_cuda_smoke` test, and I end up with an exe that is targeted at `sm_30`.

```
bash-4.2$ cuobjdump tests/blt_cuda_smoke

Fatbin elf code:
================
arch = sm_30
code version = [1,7]
producer = cuda
host = linux
compile_size = 64bit

Fatbin ptx code:
================
arch = sm_30
code version = [6,2]
producer = cuda
host = linux
compile_size = 64bit
compressed

Fatbin elf code:
================
arch = sm_30
code version = [1,7]
producer =
host = linux
compile_size = 64bit
```

Not sure how to pass flags?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the host-config settings reach the blt_cuda_smoke target, focusing on CUDA_ARCH, CMAKE_CUDA_ARCH, and CUDA_NVCC_FLAGS. Use cuobjdump on the resulting executable to compare the configured architecture with the observed sm_30 output; done means the supported setting is identified and the target uses the requested architecture.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp
Domain
build-system, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.