- 19 7月, 2017 3 次提交
- 18 7月, 2017 2 次提交
- 17 7月, 2017 8 次提交
-
-
由 Yu Yang 提交于
-
由 Yu Yang 提交于
-
由 Yu Yang 提交于
* Also fix unit test
-
由 qijun 提交于
-
由 Yan Chunwei 提交于
* add inputs * add ut for multiple inputs * fix AddToLayer * op_desc -> op_proto * CreateArgumentOffsetMap -> CreateInOutOffsetMap * move CreateInOutOffsetMap from OperatorBase to op registry * arg_idxs_ -> in_out_idxs_
-
由 Yu Yang 提交于
* Implement InferShape and register them, give a stub Kernel method by LOG(INFO)
-
由 Yu Yang 提交于
-
由 qijun 提交于
-
- 16 7月, 2017 1 次提交
-
-
由 Yu Yang 提交于
* It is used to create an operator library. It handles to split CPU and GPU sources and links operator common libraries. * It also give a reasonable warning and error when operator developer not correctly implement an operator. * Warning for lack of GPU kernel. * Same interface as `cc_library` to make code style consistent.
-
- 15 7月, 2017 1 次提交
-
-
由 liaogang 提交于
-
- 14 7月, 2017 2 次提交
-
-
由 qijun 提交于
-
由 qiaolongfei 提交于
-
- 13 7月, 2017 1 次提交
-
-
由 Yu Yang 提交于
* Convert `op` --> `operators` * Remove AddType in OpProtoMaker, because type is part of registry. * Rename CPU_OR_GPU --> DEVICE_TYPE in registry macro.
-
- 12 7月, 2017 2 次提交
-
-
由 Yu Yang 提交于
* User can register OpKernel to its Ops. The OpKernelMap saved in OperatorWithKernel. Each Op which inherits OperatorWithKernel will use `OpKernel::Compute` instead of Run.
-
由 Qiao Longfei 提交于
Add OperatorBase. issue: https://github.com/PaddlePaddle/Paddle/issues/2790 Paddle design the Operator with Kernel. OperatorBase has no type and device information when create, One operator can have multiple kernels, Operator will choose a kernel to run according to context. The kernel should be bind to Operator before or during Operator running.
-
- 11 7月, 2017 1 次提交
-
-
由 qijun 提交于
-