Skip to content

Conversation

@mgehre-amd
Copy link
Collaborator

#include make sense everywhere, and in particular we need to allow them inside a emitc.tu. But sometimes we might even want to have an #include in a function body.

`#include` make sense everywhere, and in particular we need to allow them inside a `emitc.tu`.
But sometimes we might even want to have an `#include` in a function body.
@mgehre-amd mgehre-amd requested a review from cferry-AMD November 6, 2024 16:15
Copy link
Collaborator

@cferry-AMD cferry-AMD left a comment

Choose a reason for hiding this comment

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

LGTM. Do you know of any passes that check for a specific include? Those will need to search the entire module now up to the site the include is used.

@mgehre-amd
Copy link
Collaborator Author

LGTM. Do you know of any passes that check for a specific include? Those will need to search the entire module now up to the site the include is used.

I'm not aware of any. Likely because emitc dialect is mostly generated and seldomly consumed.

@mgehre-amd mgehre-amd merged commit 26a9787 into feature/fused-ops Nov 7, 2024
5 checks passed
@mgehre-amd mgehre-amd deleted the matthias.emitc_include_parent branch November 7, 2024 10:59
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.

3 participants