1. 06 Jan, 2020 2 commits
  2. 05 Jan, 2020 2 commits
  3. 04 Jan, 2020 4 commits
    • [REFACTOR] TVM_REGISTER_API -> TVM_REGISTER_GLOBAL (#4621) · 81523604
      TVM_REGSISTER_API is an alias of TVM_REGISTER_GLOBAL.
      In the spirit of simplify redirections, this PR removes
      the original TVM_REGISTER_API macro and directly use TVM_REGISTER_GLOBAL.
      
      This type of refactor will also simplify the IDE navigation tools
      such as FFI navigator to provide better code reading experiences.
      
      Move EnvFunc's definition to node.
      Tianqi Chen committed
    • [REFACTOR] Unified IR base types. (#4616) · 1ecd3ee2
      This PR moves a few base types from relay to the ir sub-folder.
      These types will serve as a common type system across the stack.
      
      Notably, we want to be able to use the same FuncType for all function signatures.
      I tried to make a minimum move to bring the necessary dependencies for a FuncType.
      We can discuss what additional things we want to move as a follow-up.
      
      Notably, because the TensorType will have a dependency on low-level Expr,
      we will need to break the type.h into two files and introduce a
      tensor_type.h(or leave them in relay for now).
      Tianqi Chen committed
    • [REFACTOR][TYPE] Remove un-necessary var sub-field in GlobalTypeVar and TypeVar (#4615) · 24e6fcb6
      Currently, we use a tvm::Var to represent a placeholder for shapes in generic types.
      This is not necessary for GlobalTypeVar(as we never parameterize by shape var),
      and is a bit twisted for TypeVar.
      
      As we move to a unified type system, we want to break the dependency
      from the base TypeVar(which is shared across the languages) from the expression.
      Note that it is fine for TensorType to depend on Expr.
      
      One alternative solution to embed the Var would be to introduce a TypeVarExpr,
      which can wrap a TypeVar as Expr. However, this new alternative won't be
      natural until we migrate the type to the global scope.
      
      Lucikly, we have not yet start to depend on the shape parameterization heavily yet.
      
      This PR removes the tvm::Var from the typevars. We will follow up with another
      PR to migrate the types to a base location. After that, we should be able to
      use the more elegant approach via TypeVarExpr.
      Tianqi Chen committed
    • [Relay][Pass]Improve memory_allocation pass to support multiple i/o dynamic kernels (#4595) · 9c638f06
      * Add more shape funcs
      
      * Fix test
      
      * Enhance test_any_concat
      
      * Fix pylint
      
      * Minor fix test
      
      * Fix pylint
      
      * Minor refactor
      
      * Add test any for elemwise
      Yao Wang committed
  4. 03 Jan, 2020 9 commits
  5. 02 Jan, 2020 2 commits
    • [IR] Unify approach to Visitor/Mutator under Functor (#4606) · 983eba88
      IRMutator and IRVisitor were the main data structures for doing low level IR visiting.
      As the project evolves, we start to introduce more powerful variants such as StmtFunctor and ExprFunctor.
      This PR brings new classes that allows us to migrate the visitor mutator to be sub-class of these functors.
      
      List of changes:
      
      - Create separate class for ExprMutator and StmtMutator, following convention used in relay.
      - Introduce copy-on-write to StmtMutator that can later benefit the statement mutations
        if we use move semantics and keep a single copy of stmt.
      - Move two generic visit mutate util to use the new classes.
      
      We will send followup PRs to migrate the existing passes that use the legacy visitors
      to the new one.
      Tianqi Chen committed
  6. 01 Jan, 2020 2 commits
  7. 31 Dec, 2019 3 commits
  8. 30 Dec, 2019 3 commits
    • [REFACTOR][RUNTIME] Update NDArray use the Unified Object System (#4581) · 55bd786f
      * [REFACTOR][RUNTIME] Move NDArray to Object System.
      
      Previously NDArray has its own object reference counting mechanism.
      This PR migrates NDArray to the unified object protocol.
      
      The calling convention of NDArray remained intact.
      That means NDArray still has its own type_code and
      its handle is still DLTensor compatible.
      
      In order to do so, this PR added a few minimum runtime type
      detection in TVMArgValue and RetValue only when the corresponding
      type is a base type(ObjectRef) that could also refer to NDArray.
      
      This means that even if we return a base reference object ObjectRef
      which refers to the NDArray. The type_code will still be translated
      correctly as kNDArrayContainer.
      If we assign a non-base type(say Expr) that we know is not compatible
      with NDArray during compile time, no runtime type detection will be performed.
      
      This PR also adopts the object protocol for NDArray sub-classing and
      removed the legacy NDArray subclass protocol.
      Examples in apps/extension are now updated to reflect that.
      
      Making NDArray as an Object brings all the benefits of the object system.
      For example, we can now use the Array container to store NDArrays.
      
      * Address review comments
      Tianqi Chen committed
    • fix codegenc (#4597) · 4072396e
      Zhi committed
  9. 29 Dec, 2019 2 commits
  10. 28 Dec, 2019 2 commits
  11. 27 Dec, 2019 4 commits
  12. 26 Dec, 2019 5 commits