-
Notifications
You must be signed in to change notification settings - Fork 112
Create op. builders (4.) #4385
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
base: develop
Are you sure you want to change the base?
Create op. builders (4.) #4385
Conversation
… op-builder class
…er multiple numbers of op-builders
…is essentially the same how add_instruction is called a few lines above
…hat the tests run not for only one kind of binary operator
… parameter optional on the op-builder side
…erence would be there
…a default value for the 'options' parameter for an op-builder
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #4385 +/- ##
===========================================
+ Coverage 92.18% 92.24% +0.06%
===========================================
Files 560 563 +3
Lines 26641 27274 +633
===========================================
+ Hits 24558 25158 +600
- Misses 2083 2116 +33
🚀 New features to boost your workflow:
|
…tor as it arrives; in case of the TF parser we have to modify the input vector that will be passed to the op-builder. We won't need the last item.
…e-parameter functions
…-op op-builder and modify tests accrodingly
…ucing default op-builder when it's not amongst the registered ones
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 30 out of 30 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
…ne; otherwise the wrong constructor would be called
The whole purpose of the op-builders is to factor out the main functionalities behind the current onnx parsers and put them in a separate set of files (under the folder ./src/op/builder/ ) so they could be reused in different parts of the application. That is this is mainly a refactoring task; the passing of the already existing unit and verify tests should be the proof that the refactoring left the integrity of mgr intact.
related issue: migraphx-benchmark#203
covered parsers in this PR: