Go to file
Hardy b0c2a08252
Support bang c kernel wanghailu 0927 (#43)
* fix a little bug which found by new verison CMake

* add code for support BangC language kernel , just like Cuda kernel, not
library

* add bangc kernel

* support BangC kernel

* add code for support BangC kernel

* support bangc kernel

* fix some code from reviewer

* fix code of template fumction

* add code for support bangc kernel

* fix bangc format

Co-authored-by: wanghailu <wanghailu@qiyuanlab.com>
Co-authored-by: Haojie Wang <haojie0429@gmail.com>
2022-09-30 11:01:52 +08:00
.github/workflows Add: clang format check github action 2022-08-09 17:58:12 +08:00
3rd-party add code for backtrace (#21) 2022-09-01 20:30:12 +08:00
include Support bang c kernel wanghailu 0927 (#43) 2022-09-30 11:01:52 +08:00
proto Tensor serialization (#25) 2022-09-13 11:27:41 +08:00
python Add python interface for CUDA operator evaluation (#42) 2022-09-27 10:41:12 +08:00
src Support bang c kernel wanghailu 0927 (#43) 2022-09-30 11:01:52 +08:00
test Support bang c kernel wanghailu 0927 (#43) 2022-09-30 11:01:52 +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 Fix: PerfRecord in shared pointers (#31) 2022-09-18 20:27:18 +08:00
.gitmodules add code for backtrace (#21) 2022-09-01 20:30:12 +08:00
CMakeLists.txt Support bang c kernel wanghailu 0927 (#43) 2022-09-30 11:01:52 +08:00
LICENSE Initial commit 2022-07-27 22:40:23 +08:00
README.md Update README.md 2022-09-22 17:38:15 +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

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. Currently, CI on Github only checks code format. 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.