-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Bug] Heterogeneous Execution Get "target" Bug Introduced by #7518 #8536
Comments
@jroesch this might be the root cause of the issue I mentioned in the forum days ago. |
Johnson9009
added a commit
to Johnson9009/tvm
that referenced
this issue
Jul 23, 2021
Johnson9009
added a commit
to Johnson9009/tvm
that referenced
this issue
Jul 23, 2021
tqchen
pushed a commit
that referenced
this issue
Jul 29, 2021
ylc
pushed a commit
to ylc/tvm
that referenced
this issue
Sep 29, 2021
ylc
pushed a commit
to ylc/tvm
that referenced
this issue
Jan 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found the bug when sync the latest TVM commits into our own repo, after that lots of our test cases are failed.
The bug will cause the case that all of the operators are annotated to executed on a custom device fail, because the "target" is set to "llvm" incorrectly instead of the custom target like "xxpu".
Even through the root cause of the failure is difficult to describe and understand, but the bug is very obvious.
Before changes of #7518.
After changes of #7518.
I think the authors of #7518 is mislead by the code
call_dev_name = "llvm";
, if we set the target dictionary to{"cpu": "llvm", "xxpu": "xxpu"}
when call "relay.build", then the size oftargets_
at above code is 3 instead of 2, the 0th item oftargets_
maybe is "xxpu", so here the call_dev_type can't be changed to kDLCPU.@csullivan @jroesch @tqchen
The text was updated successfully, but these errors were encountered: