Small vector relocation #8
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The major changes include:
- Necessary changes to CMake files to accommodate changes due to the split of the original LCI library into two libraries (LCI and LCT).
- A new performance counters and logging infrastructure based on LCT (currently only applied to the lci pp).
- Controlled by CMake variables HPX_WITH_PARCELPORT_LCI_PCOUNTER and HPX_WITH_PARCELPORT_LCI_LOG. The default is OFF.
- New LCI parcelport configurations:
- reg_mem: whether to explicitly register memory buffers for long messages (value 1) or just let LCI register them on the fly (value 0). The default is 1.
- ndevices: how many LCI devices (low-level network contexts) to use. The default is 2.
- ncomps: how many completion managers to use. The default is 1.
6336: More cleaning up for module levels 19-20 r=hkaiser a=hkaiser Co-authored-by: Hartmut Kaiser <[email protected]>
6363: Update the lci parcelport to use LCI v1.7.6 r=hkaiser a=JiakunYan The major changes include: - Necessary changes to CMake files to accommodate changes due to the split of the original LCI library into two libraries (LCI and LCT). - A new performance counters and logging infrastructure based on LCT (currently only applied to the lci pp). - Controlled by CMake variables `HPX_WITH_PARCELPORT_LCI_PCOUNTER` and `HPX_WITH_PARCELPORT_LCI_LOG`. The default is `OFF`. - New LCI parcelport configurations: - `reg_mem`: whether to explicitly register memory buffers for long messages (value 1) or just let LCI register them on the fly (value 0). The default is 1. - `ndevices`: how many LCI devices (low-level network contexts) to use. The default is 2. - `ncomps`: how many completion managers to use. The default is 1. Co-authored-by: Jiakun Yan <[email protected]>
6369: working issue with MPI_CC / CC conflict in automake r=hkaiser a=ct-clmsn
Fixes #
An issue with MPI_CC/CC conflict with gasnet-conduit-mpi autotools (autoconf in gasnet).
## Proposed Changes
- set MPI_CC to the user set CMAKE_C_COMPILER
- set ENV{MPI_CC} to CMAKE_C_COMPILER
- set MPI_C_COMPILER to CMAKE_C_COMPILER
## Any background context you want to provide?
When gasnet compiles it automatically detects for mpi. If it finds MPI then MPI_CC is set. If MPI_CC is set to a compiler that does not match the CMAKE_C_COMPILER set by a user to compile gasnet, then a runtime exception happens during gasnet's build.
## Checklist
Not all points below apply to all pull requests.
- [ ] I have added a new feature and have added tests to go along with it.
- [ ] I have fixed a bug and have added a regression test.
- [ ] I have added a test using random numbers; I have made sure it uses a seed, and that random numbers generated are valid inputs for the tests.
Co-authored-by: ct-clmsn <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.