Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[flang][runtime] Further work on speeding up work queue operations#149189

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
klausler merged 1 commit intollvm:mainfromklausler:faster-wq
Jul 18, 2025

Conversation

klausler
Copy link
Contributor

This patch avoids a trip through the work queue engine for cases on a CPU where finalization and destruction actions during assignment were handled without enqueueing another task.

This patch avoids a trip through the work queue engine for caseson a CPU where finalization and destruction actions during assignmentwere handled without enqueueing another task.
Copy link
Contributor

@akuhlensakuhlens left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -279,13 +279,15 @@ RT_API_ATTRS int AssignTicket::Begin(WorkQueue &workQueue) {
if (mustDeallocateLHS) {
// Convert the LHS into a temporary, then make it look deallocated.
toDeallocate_ = &tempDescriptor_.descriptor();
persist_ = true; // tempDescriptor_ state must outlive child tickets
Copy link
Contributor

Choose a reason for hiding this comment

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

The general idea here is that by delaying conditionally setting persist, we can avoid persisting the allocation under some conditions and avoid the overhead of a trip through the work queue in those cases, correct?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Actually, it was being set unconditionally, so it would be true even when the child task was run immediately asBeginDestroy or whatever, and that caused a later no-op suspension and resumption.

eugeneepshteyn reacted with thumbs up emoji
@klauslerklausler merged commit97a8476 intollvm:mainJul 18, 2025
10 checks passed
@klauslerklausler deleted the faster-wq branchJuly 18, 2025 20:44
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@akuhlensakuhlensakuhlens approved these changes

@eugeneepshteyneugeneepshteyneugeneepshteyn approved these changes

@vzakharivzakhariAwaiting requested review from vzakhari

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@klausler@akuhlens@eugeneepshteyn

[8]ページ先頭

©2009-2025 Movatter.jp