Skip to content

Forward-merge release/26.06 into main#1293

Open
rapids-bot[bot] wants to merge 1 commit into
mainfrom
release/26.06
Open

Forward-merge release/26.06 into main#1293
rapids-bot[bot] wants to merge 1 commit into
mainfrom
release/26.06

Conversation

@rapids-bot
Copy link
Copy Markdown
Contributor

@rapids-bot rapids-bot Bot commented May 25, 2026

Forward-merge triggered by push to release/26.06 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

This PR cleans  #1252, so only the changes related to the OpenMP are present.

## Original description:

`run_concurrent` in `cpp/src/pdlp/solve.cu` now dispatches the barrier and dual simplex workers as `#pragma omp task` inside a `#pragma omp taskgroup` instead of raw `std::thread`. PDLP still runs synchronously on the dispatching thread.

MIP path (`omp_in_parallel()`): reuses the upstream `solve_mip` OMP team. Barrier and dual simplex now consume slots from the configured `num_cpu_threads` budget instead of spawning extra OS threads outside it.
Stand-alone LP path: stands up a local `#pragma omp parallel + single` with the right number of workers.

This PR also removes the confuscated `std::future` logic on the barrier on other PR.

Authors:
  - Nicolas L. Guidotti (https://github.com/nguidotti)
  - Akif ÇÖRDÜK (https://github.com/akifcorduk)

Approvers:
  - Alice Boucher (https://github.com/aliceb-nv)

URL: #1291
@rapids-bot rapids-bot Bot requested a review from a team as a code owner May 25, 2026 09:02
@rapids-bot rapids-bot Bot requested review from mlubin and nguidotti May 25, 2026 09:02
@rapids-bot
Copy link
Copy Markdown
Contributor Author

rapids-bot Bot commented May 25, 2026

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

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.

1 participant