-
Notifications
You must be signed in to change notification settings - Fork 81
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Target Features RFC #78
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Mousius added a question. would you like to discuss at a Community Meeting?
The `Target` can be directly inspected: | ||
|
||
```python | ||
if target.features.dsp: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we adopt any namespacing? if so how would we represent that with this syntax?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hopeful for the initial pass we can work with target.features.X
rather than further namespacing - most of what I've seen in other compilers is a flat array seems to work.
Happy to do a quick update on where this went 😸 |
If we add another member to |
The hope is to use the target parser to parse out the features as it'd just be an additional field we can set: target_json.Set("features", features_map); |
This adds a generated property "features" to the `Target` which can contain a read-only list of available features in line with apache/tvm-rfcs#78. Features are re-generated upon parsing into a `Target` object rather than being attached as `attrs`. The `Target` JSON is therefore stored without the inferred `features` attached.
This adds a generated property "features" to the `Target` which can contain a read-only list of available features in line with apache/tvm-rfcs#78. Features are re-generated upon parsing into a `Target` object rather than being attached as `attrs`. The `Target` JSON is therefore stored without the inferred `features` attached.
This adds a generated property "features" to the `Target` which can contain a read-only list of available features in line with apache/tvm-rfcs#78. Features are re-generated upon parsing into a `Target` object rather than being attached as `attrs`. The `Target` JSON is therefore stored without the inferred `features` attached.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's call this accepted since we're implementing it :)
This adds a generated property "features" to the `Target` which can contain a read-only list of available features in line with apache/tvm-rfcs#78. Features are re-generated upon parsing into a `Target` object rather than being attached as `attrs`. The `Target` JSON is therefore stored without the inferred `features` attached.
This adds a generated property "features" to the `Target` which can contain a read-only list of available features in line with apache/tvm-rfcs#78. Features are re-generated upon parsing into a `Target` object rather than being attached as `attrs`. The `Target` JSON is therefore stored without the inferred `features` attached.
No description provided.