You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that we have a few TODO items in the directory structure. Can we remove those and also remove any that are just a TODO? Doesn't look all that professional otherwise.
Remove TODO at the end:
├── bundled_program # Utilities for attaching reference inputs and outputs to models. TODO move to extension
├── codegen # Tooling to autogenerate bindings between kernels and the runtime. TODO move to tool
├── profiler # Utilities for profiling. TODO delete in favor of ETDump in sdk/
├── schema # ExecuTorch program definition, TODO move under serialization/
so you get
├── bundled_program # Utilities for attaching reference inputs and outputs to models
├── codegen # Tooling to autogenerate bindings between kernels and the runtime
├── profiler # Utilities for profiling
├── schema # ExecuTorch program definition
Remove completely (from that directory structure list in README):
├── configurations # TODO delete this
├── util # TODO delete this
Here is the full directory structure as listed right now for reference:
executorch
├── backends # Backend delegate implementations.
├── build # Utilities for managing the build system.
├── bundled_program # Utilities for attaching reference inputs and outputs to models. TODO move to extension
├── codegen # Tooling to autogenerate bindings between kernels and the runtime. TODO move to tool
├── configurations # TODO delete this
├── docs # Static docs tooling
├── examples # Examples of various user flows, such as model export, delegates, and runtime execution.
├── exir # Ahead of time library, model capture and lowering apis.
| ├── _serialize # Serialize final export artifact.
| ├── backend # Backend delegate ahead of time APIs
| ├── capture # Program capture.
| ├── dialects # Op sets for various dialects in the export process.
| ├── emit # Conversion from ExportedProgram to ExecuTorch execution instructions.
| ├── passes # Built-in compiler passes.
| ├── program # Export artifacts.
| ├── verification # IR verification.
├── extension # Extensions built on top of the runtime.
| ├── aten_util
| ├── data_loader # 1st party data loader implementations.
| ├── memory_allocator # 1st party memory allocator implementations.
| ├── pybindings # Python api for executorch runtime.
| ├── pytree # C++ and Python flattening and unflattening lib for pytrees.
| ├── testing_util
├── kernels # 1st party kernel implementations.
| ├── aten
| ├── optimized
| ├── portable # Reference implementations of ATen operators.
| ├── prim_ops # Special ops used in executorch runtime for control flow and symbolic primitives.
| ├── quantized
├── profiler # Utilities for profiling. TODO delete in favor of ETDump in sdk/
├── runtime # core cpp runtime of executorch
| ├── backend # Backend delegate runtime APIs
| ├── core # Core structures used across all levels of the runtime
| ├── executor # Model loading, initalization, and execution.
| ├── kernel # Kernel registration and management.
| ├── platform # Layer between architecture specific code and user calls.
├── schema # ExecuTorch program definition, TODO move under serialization/
├── scripts # Utility scripts for size management, dependency management, etc.
├── sdk # Model profiling, debugging, and introspection.
├── shim # Compatibility layer between OSS and Internal builds
├── test # Broad scoped end2end tests
├── third-party # third-party dependencies
├── util # TODO delete this
I've noticed that we have a few TODO items in the directory structure. Can we remove those and also remove any that are just a TODO? Doesn't look all that professional otherwise.
Remove TODO at the end:
so you get
Remove completely (from that directory structure list in README):
Here is the full directory structure as listed right now for reference:
cc @mergennachin @byjlw
The text was updated successfully, but these errors were encountered: