[Lite Interpreter] Serialize/deserialize/run __setstate__#33295
[Lite Interpreter] Serialize/deserialize/run __setstate__#33295iseeyuan wants to merge 6 commits intogh/iseeyuan/48/basefrom
Conversation
💊 CircleCI build failures summary and remediationsAs of commit 040a75b: None of the build failures appear to be your fault.
Detailed failure analysisOne may explore the probable reasons each build failed interactively on the Dr. CI website. 🚧 1 upstream failure recognized by patterns:These builds matched patterns, but were probably caused by upstream breakages:
This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions on the GitHub issue tracker. This comment has been revised 27 times. |
| .op("quantized::linear_prepack_fp16(Tensor W, Tensor? B=None) -> Tensor W_prepack", | ||
| c10::RegisterOperators::options().kernel<QLinearPackWeightFp16>( | ||
| DispatchKey::CPUTensorId)) | ||
| .op("_quantized::linear_prepack(Tensor W, Tensor? B=None) -> Tensor W_prepack", |
There was a problem hiding this comment.
why do you need to register these ops twice?
There was a problem hiding this comment.
It's a temporary solution and will be removed. Currently all lite interpreter ops are prefixed with "" because the same ops may be already registered in JIT that were not searchable from lite interpreter. To make them build together for unit tests we have this naming hack cc @smessmer . The "" will be removed after we have all ops searchable.
|
The logic around setstate looks reasonable to me! |
|
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
Stack from ghstack: