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
Fix QA issues of the devtools README (#5963)
Summary:
Pull Request resolved: #5963
Add new files in the "Directory structure".
And also remove an old statement. Since `-DEXECUTORCH_BUILD_DEVTOOLS=ON` is set in the build_example_runner.sh, and not in a command in the readme, so it no longer makes sense to call it out in this readme.
Reviewed By: Gasoonjia
Differential Revision: D64017662
fbshipit-source-id: 1ee8b086180c7f995ff3306ebceb4afcff934214
(cherry picked from commit 085193e)
Co-authored-by: Olivia Liu <[email protected]>
After exporting a `BundledProgram`, runtime profiling and debug data can be collected in an ``ETDump``. An ``ETDump`` is a buffer containing data generated by hooks within the ExecuTorch runtime.
47
50
We offer an example runner that accepts a `BundledProgram` (`.bpte`) and runs a single iteration over the first method defined.
48
51
49
-
Running the program will generate an `ETDump` file (`.etdp`) at the location specified by `--etdump_path`. Make sure to build the program as specified below to enable the event tracer.
52
+
Running the program will generate an `ETDump` file (`.etdp`) at the location specified by `--etdump_path`.
0 commit comments