Add prims.clone

[IvanYashchuk]

This simple PR adds clone as a primitive.
Current implementation of clone is not supported with nvFuser executor because of empty_like + copy_to.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

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

✅ No Failures, 1 Pending

As of commit e0ac22f:
💚 Looks good so far! There are no failures yet. 💚

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

[IvanYashchuk]

Is it okay to make clone a primitive?

[mruberry]

Making clone a prim makes sense, we should probably target the prims to being functional

Are the test failures related?

[IvanYashchuk]

Seems related.

=================================== FAILURES ===================================
_____ TestFakeTensorCUDA.test_fake_crossref_backward_amp_roll_cuda_float32 _____
Unexpected success

ERROR [0.169s]: test_make_fx_symbolic_exhaustive_matmul_cpu_float32 (__main__.TestProxyTensorOpInfoCPU)
ValueError: Cannot view a tensor with shape torch.Size([t1.size(0), t1.size(0), t0.size(0)]) and strides (t1.stride(0), 1, t1.size(0)) as a tensor with shape (t1.size(0)**2, t0.size(0))!

[IvanYashchuk]

@pytorchbot merge -g

[pytorchmergebot]

Merge started

Your change will be merged once all checks on your PR pass since you used the green (-g) flag (ETA: 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[github-actions]

Hey @IvanYashchuk.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.