Go to file
YdrMaster 45a3cdfa30 feat: GraphObj 增加一个拓扑排序方法及其测试
Signed-off-by: YdrMaster <ydrml@hotmail.com>
2023-03-15 15:09:12 +08:00
.github/workflows fix: revert ci yml 2023-02-15 07:45:21 +08:00
3rd-party test: enhance ci (#62) 2023-02-12 00:01:36 +08:00
include feat: GraphObj 增加一个拓扑排序方法及其测试 2023-03-15 15:09:12 +08:00
proto Tensor serialization (#25) 2022-09-13 11:27:41 +08:00
pyinfinitensor fix: 移除 c++ 中的中文注释,python TODO 改 FIXME 2023-03-15 14:48:39 +08:00
python Add search engine (#64) 2023-02-12 18:27:52 +08:00
src feat: GraphObj 增加一个拓扑排序方法及其测试 2023-03-15 15:09:12 +08:00
test feat: GraphObj 增加一个拓扑排序方法及其测试 2023-03-15 15:09:12 +08:00
.clang-format Add: graph, tensor, and operator 2022-07-31 21:44:03 +08:00
.cmake-format.json Add: graph, tensor, and operator 2022-07-31 21:44:03 +08:00
.gitignore feat: 创建 pyinfinitensor 前端 2023-02-13 09:19:05 +08:00
.gitmodules add code for backtrace (#21) 2022-09-01 20:30:12 +08:00
CMakeLists.txt feat: 创建 pyinfinitensor 前端 2023-02-13 09:19:05 +08:00
LICENSE Initial commit 2022-07-27 22:40:23 +08:00
Makefile feat: 创建 pyinfinitensor 前端 2023-02-13 09:19:05 +08:00
README.md test: enhance ci (#62) 2023-02-12 00:01:36 +08:00

README.md

InfiniTensor

Compilation on Lotus

# Enter the root of InfiniTensor
source test/script/env_lotus.sh
mkdir build && cd build
cmake -DUSE_CUDA=ON .. && make -j 12

CMake Options

There are several configurable CMake options, see the CMakeLists.txt file.

  • If USE_BACKTRACE is ON, libdw-dev have to be installed. See the README of backward-cpp for details.
  • If USE_PROTOBUF is ON, protobuf have to be installed. See the README of protobuf for details.

Contributor Guide

InfiniTensor development is based on the pull request on Github. Before requesting for merging, a PR should satisfy the following requirements

  1. Pass all tests.
    1. Now CI on Github will test everything that can be tested in the ci environment, including code format. So, script test/script/clang_format_inplace.sh is for formatting all code.
    2. Contributors should run ctest manually and copy its output to the PR. Use fenced code blocks (triple backquotes, i.e., ```) to avoid referencing in Github. Otherwise, # in the output is interpreted as a Github reference. Do not directly paste the ctest output in commit messages either for the same reason.
  2. Receive at least one approval from reviewers.
  3. PR title should be concise since it is going to be the commit message in the main branch after merging and squashing.

Dependencies