Skip to content
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

Merged
merged 1 commit into from
Aug 22, 2022
Merged

Add Target Features RFC #78

merged 1 commit into from
Aug 22, 2022

Conversation

Mousius
Copy link
Member

@Mousius Mousius commented Jun 9, 2022

No description provided.

@areusch
Copy link
Contributor

areusch commented Jun 10, 2022

Copy link
Contributor

@areusch areusch left a 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:
Copy link
Contributor

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?

Copy link
Member Author

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.

@Mousius
Copy link
Member Author

Mousius commented Jun 29, 2022

@Mousius added a question. would you like to discuss at a Community Meeting?

Happy to do a quick update on where this went 😸

@kparzysz-quic
Copy link

If we add another member to Target, how will this interact with the target parser proposal?

@Mousius
Copy link
Member Author

Mousius commented Jul 15, 2022

If we add another member to Target, how will this interact with the target parser proposal?

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);

Mousius added a commit to Mousius/tvm that referenced this pull request Jul 18, 2022
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.
Mousius added a commit to Mousius/tvm that referenced this pull request Jul 19, 2022
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.
kparzysz-quic pushed a commit to apache/tvm that referenced this pull request Jul 19, 2022
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.
Copy link
Contributor

@areusch areusch left a 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 :)

@areusch areusch merged commit 1ab898d into apache:main Aug 22, 2022
xinetzone pushed a commit to daobook/tvm that referenced this pull request Nov 25, 2022
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.
mikeseven pushed a commit to mikeseven/tvm that referenced this pull request Sep 27, 2023
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.
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