llnl / llnl/CHAI

More configuration checking

Open
#225 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
111
Forks
23
Avg merge
2d 7h
Merged PRs (30d)
4

Description

Should CHAI_ENABLE_PINNED=ON be a configuration error if CUDA/HIP/GPU simulation mode are all disabled?
Should CHAI_ENABLE_UM=ON be a configuration error if CUDA/HIP/GPU simulation mode are all disabled?

Also, if CUDA/HIP/GPU simulation mode are all disabled, should the resource manager be required to be off?

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

No files, tests, or entry points are named. Start by locating the configuration definitions for CHAI_ENABLE_PINNED, CHAI_ENABLE_UM, CUDA/HIP/GPU simulation mode, and the resource manager. The work is done when the intended invalid combinations are decided and configuration checking consistently reports them.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.