Improve ONNX 1.14 compatibility #134
Merged
Conversation
This file contains 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
onnx 1.15 introduced some performance optimizations. We can forego their usage if onnx<1.15 without loss of functionality.
adityagoel4512
requested changes
Feb 7, 2024
adityagoel4512
approved these changes
Feb 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ONNX 1.15 introduced some performance optimizations which we are using since
0.10. We can forego their usage ifonnx<1.15without loss of functionality to avoid a version bound.Since Spox exports the ONNX standard which expands with each (minor) release, we can't claim full compatibility with older versions.
Checklist
CHANGELOG.rstentry