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 int8 padding operator and unit tests #149

Closed
wants to merge 0 commits into from

Conversation

AdrianLundell
Copy link
Collaborator

No description provided.

README.md Outdated
@@ -38,6 +38,7 @@ Examples are Cortex-M55 or Cortex-M85 configured with MVE.
| Softmax | Yes | Yes | N/A | Yes | Yes | N/A | Yes | No | N/A |
| LSTM | Yes | Yes | No | Yes | Yes | No | Yes | Yes | No |
| SVDF | Yes | No | No | Yes | No | No | Yes | No | No |
| Pad | Yes | No | No | Yes | No | No | Yes | No | No |
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be N/A instead of No as no weights

Copy link
Collaborator

@ArmRyan ArmRyan Oct 16, 2024

Choose a reason for hiding this comment

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

I think no is the right one here, because it is possible to have int16 padding for example but we do not have the support for it? It seems like this table is not intended for weights but rather base operator support. I would personally argue that we should replace all N/A with no

Copy link
Contributor

Choose a reason for hiding this comment

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

int16 padding would mean input and output in int16, right? That is second column with a No already

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