Arm backend: Auto generate cycle table if ETDump is used

[zingo]

Summary

If you use run.sh with --etdump e.g. something like this:

examples/arm/run.sh --et_build_root=arm_test/test_run --target=ethos-u55-256 --model_name=mv2 --etdump

The script will dig out the ETDump file from the FVP logs and use it to produce a cycle table automatically.

Please remember the the CorstoneFVP is not a cycle accurate simulator and the CPU cycle numbers can not be trusted, please run on real hardware or FPGA to get valid number. Running it on a FVP is mostly useful to check that the tools/flow work and not the actual CPU cycle numbers.

Test plan

This is tested by the test scripts

cc @digantdesai @freddan80 @per @oscarandersson8218

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13943

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 4 New Failures, 1 Pending

As of commit 07c0eb4 with merge base f6d90ef ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  At least one of the pre-conditions you specified did not hold
• pull / unittest / macos / macos-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• pull / unittest-editable / macos / macos-job (gh)
  backends/xnnpack/test/recipes/test_xnnpack_recipes.py::TestXnnpackRecipes::test_int8_static_quant_recipe
• trunk / unittest-release / macos / macos-job (gh)
  backends/xnnpack/test/ops/test_rsqrt.py::TestRsqrt::test_fp16_rsqrt

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[oscarandersson8218]

Looks good to me. CI failures seem unrelated.