Skip to content

[NNNN] New proposal for organizing intrinsic tickets#379

Open
kmpeng wants to merge 4 commits intollvm:mainfrom
kmpeng:organizing-intrinsic-tickets
Open

[NNNN] New proposal for organizing intrinsic tickets#379
kmpeng wants to merge 4 commits intollvm:mainfrom
kmpeng:organizing-intrinsic-tickets

Conversation

@kmpeng
Copy link

@kmpeng kmpeng commented Jan 26, 2026

Related to #377.

This proposal suggests how we should reorganize our implementation and offload test tickets for intrinsics.

Copy link
Collaborator

@damyanp damyanp left a comment

Choose a reason for hiding this comment

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

Added some questions.

I think we should also cover here how much detail we go into for each issue. I think we had too much for the ones we did previously, resulting in some of it being confusingly irrelevant to the actual issue itself.

@farzonl
Copy link
Member

farzonl commented Jan 27, 2026

My general thoughts on this is we have 4 classes of tickets we need to track for completion status.

  • Completed intrinsics issue that need matrix implementations and completed or nonexistant offload tests
    • Create new llvm-project issues to track matrix implementation
    • Create new offload suite issues to track testing completion
    • Need to link tests in llvm-project issue
  • Open intrinsic tickets that need matrix and Completed or nonexistant offload tests
    • Update the open ticket with the matrix requirements
    • Create the offload suite issue
    • link the offload suite issue in the llvm-project issue
  • Open Intrinsic and Open offload suite test
    • Update both tickets to cover matrix testing requirement
  • Completed offload tests but no intrinsic implementation in clang
    • Just update the llvm issue with the matrix requirements
    • Create a new issue for the offload suite to cover matrix requirements

Ideally we could just parent the offload test to the llvm-project issue, but I suppose if you want to track implementation and test progress seperately you could parent to a new offload test suite issue that links to all the new offload tests we created.



## Questions
1) What are the categories we can group the intrinsics into? No newline at end of file
Copy link
Member

@farzonl farzonl Feb 10, 2026

Choose a reason for hiding this comment

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

Delete this? We should have all questions answered at this point right?

Copy link
Author

Choose a reason for hiding this comment

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

We never answered this. I can follow up in the chat about it.

@@ -0,0 +1,96 @@
---
title: "[NNNN] - Organizing Intrinsic Tickets"
Copy link
Member

Choose a reason for hiding this comment

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

add a number before merging here and in the title of this pr

Copy link
Author

Choose a reason for hiding this comment

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

FYI Damyan and I came to the conclusion we don't actually want to merge this, just wanted it updated for documentation. I was going to close it once the reorganization is completed.

params:
authors:
- kmpeng: Kaitlin Peng
status: Under Consideration
Copy link
Member

Choose a reason for hiding this comment

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

move to Accepted

Copy link
Member

@farzonl farzonl left a comment

Choose a reason for hiding this comment

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

LGTM

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.

4 participants

Comments