aoti_torch_create_tensor_from_blob_v2

[larryliu0820]

Stack from ghstack (oldest at bottom):

• use ET_CHECK macro for sanity checks in memory shim layer #14690
• aoti_torch_copy_ #14689
• aoti_torch__reinterpret_tensor #14688
• -> aoti_torch_create_tensor_from_blob_v2 #14687
• tensor destroy #14686

Summary:

This function introduce aoti_torch_create_tensor_from_blob_v2, a function that create tensor from data blob and custom stride and size.

Worth to notice that unlike aoti_torch_empty_strided, the tensor created by aoti_torch_create_tensor_from_blob_v2 will not have the control of the memory blob. Therefore when we delete it, the memory will not be freed.

Reviewed By:

Differential Revision:

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 1 New Failure, 2 Cancelled Jobs, 1 Unrelated Failure

As of commit 975fb6b with merge base db8d04f ():

NEW FAILURE - The following job has failed:

• pull / unittest-arm-backend-with-no-fvp (test_pytest_ops) / linux-job (gh)
  RuntimeError: Command docker exec -t b1469ebcbfbaa4d2bf61516103d05d7ca03bcb941c43c9adf7c886b861eb7e0d /exec failed with exit code 1

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• pull / test-binary-size-linux-gcc / linux-job (gh)
• pull / test-setup-linux-gcc / linux-job (gh)

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

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

[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.