Build errors on develop branch with OpenMP Enabled
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32
- Forks
- 7
- Avg merge
- 19h 49m
- Merged PRs (30d)
- 14
Description
I'm currently testing CARE out on an linux machine with GCC v7.5.0 compiler suite and a toss3 machine with GCC v7.3.0.
I'm finding that the build is failing on the TestSortFuser example with a number of errors that appear related to the RAJA execution policy for example here's one of the hard errors:
CARE/src/care/SortFuser.h:265:25: error: no matching function for call to ‘sortArray(RAJA::PolicyBaseT<(RAJA::Policy)4, (RAJA::Pattern)1, (RAJA::Launch)0, (camp::resources::v1::Platform)1, RAJA::policy::omp::Parallel, RAJA::wrapper<RAJA::policy::omp::omp_for_schedule_exec<RAJA::policy::omp::Auto> > >, care::host_device_ptr<int>&, int&)’
care::sortArray(RAJAExec{}, m_concatenated_result, m_total_length);
It should be pretty easy to reproduce on an LC machine with the following cmake invocation on commit 654b9fac6e29e6ec3fba3eeba3b5919ccf5599ba:
cmake ../ -DENABLE_OPENMP=ON -DCMAKE_INSTALL_PREFIX=../install_dir/
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the failure in the TestSortFuser example using commit 654b9fac6e29e6ec3fba3eeba3b5919ccf5599ba and the provided CMake options. Start at CARE/src/care/SortFuser.h:265 and inspect the RAJA execution-policy call shown in the error. Done means the OpenMP-enabled build completes for this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100