Feature/extern type #183
Open
Feature/extern type #183
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These can be used to interact with APIs that require us to emit types
that we do not currently support in artic, e.g. Matrix Types in SPIRV.
Currently, only the C backend supports external types. A typedef is
generated, i.e. an ExternType with args `{ "foo" }` and name `"bar"` emits
typedef foo bar;
… name collisions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AnyDSL/artic#36.
This is the bare minimum required to support external types. The only back-end implementation emits external types in the C backend, only types with a single string literal are supported, and that string literal is dumped into the output file as
typedef <id> <option>;with<option>being the supplied option verbatim. The option is not sanitized in any way!