model: Remove uses of custom linear op #303
Draft
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.
Pull Request Description
Type of Change
Changes Overview
The uses of custom linear ops are removed.
Motivation and Context
The custom linear op was introduced because it takes very long time to trace when tracing with torch.jit.trace. But now the models are now traced by torch export, so the custom linear op is not necessary anymore.
Checklist
Additional Information
Related Issues
Conventional commit
Type candidate
model: Adding New models or Bugfix for existing modelsperformance: Optimizing some models or this library itselfrefactor: Re-arrange class architecture, or more.doc: Update docstring onlydependency: Update requirements, something like that.other: None of above.