torch-mlir/include/npcomp/RefBackend/Runtime
Sean Silva 83ad70ef54 [RefBackend] Move runtime related code under npcomp/RefBackend/
Other than the dialect definitions (which will live in standard Dialect/
subdirectory), the goal here is to keep RefBackend-related code nested
in {include/npcomp,lib,test}/RefBackend.
2020-10-08 09:07:00 -07:00
..
README.md [RefBackend] Move runtime related code under npcomp/RefBackend/ 2020-10-08 09:07:00 -07:00
Support.h [RefBackend] Move runtime related code under npcomp/RefBackend/ 2020-10-08 09:07:00 -07:00
UserAPI.h [RefBackend] Move runtime related code under npcomp/RefBackend/ 2020-10-08 09:07:00 -07:00

README.md

RefBackendRt (namespace refbackrt) is the runtime support library for the RefBackend backend. It is best practice to keep compiler and runtime code totally firewalled.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! As such, this directory should have NO DEPENDENCIES ON COMPILER CODE (no LLVM libSupport, etc.). !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

This will cause some duplication, but history has shown that this firewalling pays big dividends. In particular, compiler code very frequently has binary sizes that are simply unacceptable in runtime scenarios, such as MByte-sized dependencies like LLVM libSupport. Runtime code should fit in kBytes.