mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Skalicky <notificati...@github.com>
Subject Re: [apache/incubator-mxnet] [RFC] MXNet external operators (#18904)
Date Tue, 25 Aug 2020 22:30:18 GMT
> @samskalicky, can clarify which symbols are needed for the external operators you are
interested in?

Not sufficiently, anything that anybody uses to write an internal/backend operator could be
anything in MXNet/NNVM/TVM/mshadow/etc... so if the goal of the feature is enable any backend
operator to be dynamically loaded, we have to export all symbols.

The biggest problem with individual symbol exposure many symbols needed arent entirely defined
in MXNet source code. One example is that the operator registration macro `NNVM_REGISTER_OP`
resolves to something that calls `::dmlc::Registry<::nnvm::Op>::Get()` which is defined
in **3rdparty/tvm/nnvm/src/core/op.cc**. So unless we go and modify that 3rd party code we're
stuck.

-- 
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/pull/18904#issuecomment-680301323
Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message