Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test reproducing a section of qmcpack that exercises many OpenMP … #432

Open
wants to merge 1 commit into
base: aomp-dev
Choose a base branch
from

Conversation

carlobertolli
Copy link
Contributor

…threads executing target regions multiple times.

…threads executing target regions multiple times.
Comment on lines +16 to +19
run: $(TESTNAME)
export OMP_NUM_THREADS=128
$(RUNENV) $(RUNPROF) ./$(TESTNAME) 2>&1 | tee [email protected]
unset OMP_NUM_THREADS
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Custom run rules should be handled via a RUNCMD variable.
This variable is invoked automatically from the top-level Makefile for both run and check.

You can check any of the veccopy-ompt test cases for an example.

omp_alloctrait_t pinned_trait[1] = {{omp_atk_pinned, omp_atv_true}};
omp_allocator_handle_t pinned_alloc = omp_init_allocator(omp_default_mem_space, 1, pinned_trait);
for(int t = 0; t < times; t++) {
#pragma omp parallel num_threads(128)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have this hardcoded in here, or should we rely on the runtime environment for it to be set?
I would prefer the latter, as we may want to run this as part of our testing on smaller machines as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants