-
Notifications
You must be signed in to change notification settings - Fork 159
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
[onert/odc] Auto-compilation. Input/output buffers in Execution #14383
[onert/odc] Auto-compilation. Input/output buffers in Execution #14383
Conversation
cf0fdb2
to
d3f92a4
Compare
Looks good for input/output buffer getter. |
@hseok-oh Purpose of |
Then that seems independent with ODC. Is that used in ODC? Otherwise, it may be better to handled in session (in |
@hseok-oh you are right, this structure is not used in ODC, it's used in |
…cution This PR for `odc:auto-compilation` introduces OdcInfo structure and input/output buffers in Execution. For [Issue]( Samsung#13288). From [Draft](Samsung#13530). ONE-DCO-1.0-Signed-off-by: Evgenii Maltsev [email protected]
d3f92a4
to
d6974be
Compare
Rebased this PR and deleted OdcInfo structure |
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.
LGTM
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.
LGTM! Thank you!
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.
LGTM
This PR for
odc:auto-compilation
introduces OdcInfo structure and input/output buffers in Execution.For Issue.
From Draft.
ONE-DCO-1.0-Signed-off-by: Evgenii Maltsev [email protected]