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 rankRange to opSupportLimits() #828

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

inexorabletash
Copy link
Member

@inexorabletash inexorabletash commented Mar 12, 2025

Add rankRange to opSupportLimits() by renaming MLSupportLimits to MLDataTypeLimits (still used for inputs, constants, and output operands), and deriving MLTensorLimits (used for tensor operands) which adds the new member as a MLRankRange dictionary.

This also adds a note about an operand's allowed data types and ranks, indicating the implementations may extend or impose limits.

In addition, maxTensorByteLength is added to the MLOpSupportLimits dictionary.

Based on the work in Chromium by Reilly Grant, Wei Wang, and Junwei Fu.

Resolves #456


Preview | Diff

Add rankRange to opSupportLimits() by renaming MLSupportLimits to
MLDataTypeLimits (still used for inputs, constants, and output
operands), and deriving MLTensorLimits (used for tensor operands)
which adds the new member as a MLRankRange dictionary.

This also adds a note about an operand's allowed data types and ranks,
indicating the implementations may extend or impose limits.

Finally, maxTensorByteLength is exposed at the top level of the
dictionary.
@inexorabletash inexorabletash marked this pull request as draft March 12, 2025 20:58
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.

Define the maximum number of operand dimensions (maximum rank)
1 participant