In place zero fill for Devserver FSIM debug buffer

[michaelmaitland]

Summary: Some ops are in place (index_put_ or aten_copy_). This diff makes the debug buffer flow support these cases.

Differential Revision: D86346763

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 17 New Failures, 1 Cancelled Job

As of commit 241e0e8 with merge base 5b3d9fc ():

NEW FAILURES - The following jobs have failed:

• Build Presets / apple (profiling) / build (gh)
  /Users/runner/work/executorch/executorch/pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: implicit instantiation of undefined template 'std::vector<unsigned char>'
• Build Presets / apple (pybind) / build (gh)
  /Users/runner/work/executorch/executorch/pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: implicit instantiation of undefined template 'std::vector<unsigned char>'
• Build Presets / windows (pybind) / build (gh)
  Process completed with exit code 1.
• pull / unittest / windows / windows-job (gh)
  Process completed with exit code 1.
• pull / unittest-editable / windows / windows-job (gh)
  Process completed with exit code 1.
• Test CUDA Builds / check-all-cuda-builds (gh)
  Process completed with exit code 1.
• Test CUDA Builds / test-executorch-cuda-build-12.6 / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-executorch-cuda-build-12.8 / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-executorch-cuda-build-12.9 / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-executorch-cuda-build-13.0 / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-models-cuda (add_mul) / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-models-cuda (add) / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-models-cuda (conv1d) / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-models-cuda (linear) / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-models-cuda (resnet18) / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / test-models-cuda (sdpa) / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope
• Test CUDA Builds / unittest-cuda / linux-job (gh)
  /pytorch/executorch/devtools/etdump/data_sinks/file_data_sink.cpp:59:26: error: ‘zeros’ was not declared in this scope

CANCELLED JOB - The following job was cancelled. Please retry:

• periodic (gh)

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

[meta-codesync]

@michaelmaitland has exported this pull request. If you are a Meta employee, you can view the originating Diff in D86346763.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.