Tests don't pass on 9.0.1
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start with Runtime.h and inspect the declaration of FPC_FILE_NAME and how it is located when optimizations are enabled. Compare the current declaration with the initializer shown in the issue, then run the repository's tests to confirm that they pass on 9.0.1 and that the variable remains discoverable.
Written by the indexing model from the issue text.
Description
In the Runtime.h file the following declaration causes problems:
__device__ static char *_FPC_FILE_NAME_[1];
When optimizations are applied, this global variable is lost (or optimized out), but we need to find it.
This seems to solve the problem:
__device__ const static char *_FPC_FILE_NAME_[1] = {"none"};
- Dominant language
- Python
- Stars
- 45
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from llnl/FPChecker
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
clang_plugin_branch enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
bug clang_plugin_branch
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
[oblt-aw][autodoc] Update workflow docs for gh-aw v0.92.5 and detector permission scopePossibly taken @github-actions claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
roadmap-100
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
comp/tools P2 tool/browser tool/file type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NousResearch/hermes-agent#143418 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python-hyper/uritemplate#164 ·