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.

Sign up for GitHub

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

Jump to bottom

Review use of types for number of processes and threads #3134

Open
heplesser opened this issue Mar 5, 2024 · 1 comment
Open

Review use of types for number of processes and threads #3134

heplesser opened this issue Mar 5, 2024 · 1 comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority stale Automatic marker for inactivity, please have another look here T: Maintenance Work to keep up the quality of the code and documentation.
Projects
Kernel

Comments

@heplesser
Copy link
Contributor

We currently have a bit of a mess of types for process and thread numbers, between int (e.g., MPIManager::num_processes_) and size_t (e.g., return type of MPIManager::get_num_processes()), see also #3133.

Note that relevant MPI and OpenMP functions use int for process and thread numbers, see
@heplesser heplesser added S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels Mar 5, 2024
@heplesser heplesser added this to To do (open issues) in Kernel via automation Mar 5, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented May 5, 2024

Issue automatically marked stale!

@github-actions github-actions bot added the stale Automatic marker for inactivity, please have another look here label May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority stale Automatic marker for inactivity, please have another look here T: Maintenance Work to keep up the quality of the code and documentation.
Projects
Kernel
  
To do (open issues)
Milestone
No milestone
Development

No branches or pull requests
1 participant
@heplesser