-
Notifications
You must be signed in to change notification settings - Fork 93
Introduce OpSignature to IR #1838
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
Conversation
❌ 19 Tests Failed:
View the full list of 3 ❄️ flaky tests
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
Test Results 24 files ± 0 24 suites ±0 2h 44m 6s ⏱️ + 4m 1s For more details on these failures and errors, see this check. Results for commit ff1aaa5. ± Comparison against base commit fac4825. ♻️ This comment has been updated with latest results. |
|
When the signature property is defined, PyTorch onnx exporter will not generate a new signature, and instead use what is here. However, since it is doing isinstance checks on the signature the exporter itself defines, we get isinstance errors there. |
Introduce OpSignature accessible from the
.op_signatureproperty of all OpLike objects (traced function, onnx function and op). The OpSignature class leverages the IR to represent the signature of an operator, preserving ordering of all inputs and provides easy to work with type representations.The PR also deprecates the ParamSchema class and properties.
Fixes #1697
The next PR will replace param_schemas usage.