Skip to content

[2026-03 LWG Motion 33] P3941R4 Scheduler Affinity#8925

Merged
tkoeppe merged 1 commit intomainfrom
motions-2026-03-lwg-33
Apr 20, 2026
Merged

[2026-03 LWG Motion 33] P3941R4 Scheduler Affinity#8925
tkoeppe merged 1 commit intomainfrom
motions-2026-03-lwg-33

Conversation

@jensmaurer
Copy link
Copy Markdown
Member

@jensmaurer jensmaurer commented Apr 6, 2026

Fixes NB US 232-366, US 233-365, US 234-364, US 235-363, US 236-362 (C++26 CD).

Fixes #8867

Also fixes cplusplus/papers#2594
Also fixes cplusplus/nbballot#937
Also fixes cplusplus/nbballot#938
Also fixes cplusplus/nbballot#939
Also fixes cplusplus/nbballot#940
Also fixes cplusplus/nbballot#941

@jensmaurer jensmaurer added this to the post-2026-03 milestone Apr 6, 2026
@jensmaurer jensmaurer force-pushed the motions-2026-03-lwg-33 branch from c3aed96 to 91743d3 Compare April 6, 2026 20:28
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
@jensmaurer jensmaurer force-pushed the motions-2026-03-lwg-33 branch from 33a81fb to 3ff23b5 Compare April 7, 2026 10:22
@jensmaurer jensmaurer requested a review from eisenwave April 7, 2026 10:22
Copy link
Copy Markdown
Contributor

@dietmarkuehl dietmarkuehl left a comment

Choose a reason for hiding this comment

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

I believe one change was omitted: adding the get_start_scheduler object.

Another change was potentially garbled in the paper. The paper assumed P3826 (although revision 3) was applied (first editors note) and, thus, the reference to wasn't there. get-domain-early doesn't exist anymore based on P3826r5. If the corresponding change gets applied when P3826 get applied it doesn't have to done here.

While reviewing I noticed that I didn't mark at least one of the editor's note as such and, I think, some minor fixes were applied during editing: thank you very much!

Comment thread source/exec.tex
Comment thread source/exec.tex Outdated
@jensmaurer
Copy link
Copy Markdown
Member Author

@dietmarkuehl , there are still a number of mentions of "get-domain-early", so I don't know where we are with those.

@dietmarkuehl
Copy link
Copy Markdown
Contributor

@dietmarkuehl , there are still a number of mentions of "get-domain-early", so I don't know where we are with those.

This paper isn't meant to fix these: I thought these should be fixed by P3826r5. Looking at the current PR for P3826r5 I see that currently only one place is addressed by the paper has a total of 12 places where "get-domain-early" gets removed. It seems the current [exec] wording has 14 places, though. Looking at the paper more closely: the two remaining places are removed via wording which isn't a diff: "Remove the prototypes of the get-domain-early and get-domain-late functions."

P3914R4 shouldn't reintroduce any uses of "get-domain-early" (and I don't think the wording does): there is no mention of "get-domain-early" in the changed text in the PR.

@tkoeppe tkoeppe force-pushed the motions-2026-03-lwg-33 branch from bcf5741 to c2a2cab Compare April 20, 2026 10:45
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
@tkoeppe tkoeppe force-pushed the motions-2026-03-lwg-33 branch from c2a2cab to 52ce6ab Compare April 20, 2026 11:20
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
Comment thread source/exec.tex Outdated
@tkoeppe tkoeppe force-pushed the motions-2026-03-lwg-33 branch from 52ce6ab to b0fae30 Compare April 20, 2026 12:09
Copy link
Copy Markdown
Member

@jwakely jwakely left a comment

Choose a reason for hiding this comment

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

Still some merge conflicts that were resolved in the wrong direction.

This really should have been prepared as a change on top of #8919 not on top of the main branch before merging #8919. That would have made it much easier.

@tkoeppe tkoeppe force-pushed the motions-2026-03-lwg-33 branch from b0fae30 to f25b8a9 Compare April 20, 2026 12:11
@tkoeppe tkoeppe requested review from dietmarkuehl and jwakely April 20, 2026 12:16
Fixes NB US 232-366, US 233-365, US 234-364, US 235-363, US 236-362 (C++26 CD).
@tkoeppe tkoeppe force-pushed the motions-2026-03-lwg-33 branch from 5d436bc to cb03337 Compare April 20, 2026 12:58
@tkoeppe tkoeppe merged commit 5e7bfcd into main Apr 20, 2026
4 checks passed
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.

[2026-03 LWG Motion 33] P3941R4 Scheduler Affinity P3941 R3 Scheduler Affinity

5 participants