Skip to content

Implement JIT call ordering - #3870

Open
Pangoraw wants to merge 2 commits into
mainfrom
jit/ordering
Open

Pangoraw wants to merge 2 commits into
mainfrom
jit/ordering

Conversation

@Pangoraw

@Pangoraw Pangoraw commented Nov 6, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@Pangoraw
Pangoraw requested a review from mofeing November 6, 2026 15:24
@codecov

codecov Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 29.83%. Comparing base (0e73e9d) to head (2a22cb8).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3870      +/-   ##
==========================================
- Coverage   29.88%   29.83%   -0.05%     
==========================================
  Files         249      249              
  Lines       55024    54840     -184     
==========================================
- Hits        16445    16364      -81     
+ Misses      38579    38476     -103     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Pangoraw
Pangoraw requested a review from romanlee November 6, 2026 15:33

@mofeing mofeing left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

i think we want to enforce this always and make it non-optional.

also, not all jit_calls require tokens (e.g. MPI_Comm_rank is "pure") so i would prefer marking it per-op.

Comment on lines +1684 to +1686
if (jitCall.getFnAttr().getLeafReference().getValue().starts_with(
"enzymexla_jitwrap_"))
jitCalls.push_back(jitCall);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

isn't this fragile because other unrelated jit_calls might also use the same naming convention?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

yes a bit janky, i will use an attribute just within this pass like (enzymexla.comm_jit_ordered)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

this will also fix your other comment since we will just not attach the attribute to that custom call that need not to be ordered.

This branch has not been deployed

No deployments
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.

2 participants