-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Rename GraphRuntime to GraphExecutor #7653
Conversation
µTVM note: you will need to nuke |
@d-smirnov , @lhutton1 , @mbaret : could you please take a look ? |
CMakeLists.txt
Outdated
@@ -303,12 +303,12 @@ else() | |||
list(APPEND COMPILER_SRCS ${STACKVM_RUNTIME_SRCS}) | |||
endif(USE_STACKVM_RUNTIME) | |||
|
|||
if(USE_GRAPH_RUNTIME) | |||
if(USE_GRAPH_EXECUTOR) | |||
message(STATUS "Build with Graph runtime support...") |
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.
Missed one
CMakeLists.txt
Outdated
@@ -326,7 +326,7 @@ if(USE_PROFILER) | |||
file(GLOB RUNTIME_GRAPH_DEBUG_SRCS src/runtime/graph/debug/*.cc) |
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.
missed this
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.
I think this is fine, the var name derives from the path. or do you mean we should fix path to e.g. src/runtime/graph_executor/...?
docs/install/from_source.rst
Outdated
@@ -88,7 +88,7 @@ The configuration of TVM can be modified by `config.cmake`. | |||
- On macOS, for some versions of Xcode, you need to add ``-lc++abi`` in the LDFLAGS or you'll get link errors. | |||
- Change ``set(USE_CUDA OFF)`` to ``set(USE_CUDA ON)`` to enable CUDA backend. Do the same for other backends and libraries | |||
you want to build for (OpenCL, RCOM, METAL, VULKAN, ...). | |||
- To help with debugging, ensure the embedded graph runtime and debugging functions are enabled with ``set(USE_GRAPH_RUNTIME ON)`` and ``set(USE_GRAPH_RUNTIME_DEBUG ON)`` | |||
- To help with debugging, ensure the embedded graph executor and debugging functions are enabled with ``set(USE_GRAPH_EXECUTOR ON)`` and ``set(USE_GRAPH_EXECUTOR_DEBUG ON)`` |
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.
- To help with debugging, ensure the embedded graph executor and debugging functions are enabled with ``set(USE_GRAPH_EXECUTOR ON)`` and ``set(USE_GRAPH_EXECUTOR_DEBUG ON)`` | |
- To help with debugging, ensure the embedded graph executor and debugging functions are enabled with ``set(USE_GRAPH_EXECUTOR ON)`` and ``set(USE_PROFILER ON)`` |
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.
done
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.
I think we probably need to create an alias for graph_runtime (if they are all replaced by graph_executor) and remove it in the next release for backward compatibility. We can issue a warning to when graph_runtime is used. Otherwise, I think it would break the downstream deployment once they sync with upstream TVM. Please ignore if you have it already.
ebbecd3
to
225236b
Compare
@zhiics good call. I added python backwards compatibility for the |
b0ff20a
to
bc9bab8
Compare
@areusch yeah, warning may not be needed. I was just trying to make sure that we don't break all the downstream deployment by letting them know that what is going to happen there. |
@zhiics it's definitely a breaking change, i'm not opposed to the warning or some other way to notify downstream users. I don't know if code or forum or other is the best channel for that--i'm inclined to lean towards code in case forum or elsewhere also has snippets that may become outdated. i'm happy to do whatever you propose--which way do you prefer? |
50110b3
to
2f10d74
Compare
Given we are pre-1.0 we can just do our best effort when backward compact is possible but not necessary have to spend an extra mile of effort. may not hurt to post a notice to forum as well. e.g. https://discuss.tvm.apache.org/t/notice-tvm-runtime-rpc-upgrade-in-pr7488/9237/5 |
@areusch Thanks. I also prefer code for the the same reason you mentioned. |
@zhiics I've added Python backwards-compat. Please let me know if you think this is adequate. If so, I think we are ready to merge. |
mResultView.setText(label); | ||
} | ||
Log.i(TAG, "prediction finished"); | ||
if (null != graphExecutorModule) { |
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.
Why is the indent size here is 2 while everywhere else its 4?
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.
good catch @cnv1989, I had run git-clang-format directly rather than with the script, and it looks like it affected java files. reverted.
3ce0117
to
f5b48b6
Compare
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.
f5b48b6
to
acd8db1
Compare
oops. sorry there is a merge conflict due to another renaming PR. @areusch can you rebase. will prioritize merging this |
2bf1d69
to
a269414
Compare
e002487
to
bf02d29
Compare
bf02d29
to
40e797b
Compare
Fix graph runtime -> graph executor
Fix graph runtime -> graph executor lint
Fix graph runtime -> graph executor lint
Following TVM's rename in apache/tvm#7653, update to avoid errors when tvm.contrib.graph_runtime is removed entirely.
Following TVM's rename in apache/tvm#7653, update to avoid errors when tvm.contrib.graph_runtime is removed entirely.
This PR implements the "GraphRuntime" part of [RFC] Rename GraphRuntime and ilk to e.g. GraphExecutor. It's quite invasive, so it would be great if everyone could look it over. I think this PR is almost entirely targeted find-replace, as shown by the commit history.
one thing I noticed: @u99127 to look at ARM Compute Lib changes, i'm not sure how you prefer to notate ARM compute lib.
@tqchen @jroesch @junrushao1994 @tkonolige @zhiics @manupa-arm @ZihengJiang