Reland 3 of Merge more symbolic meta kernels and symint changes from branch

[albanD]

Take 3
Contains:

• symintification of split*
• floor support on SymFloat
• pad_backward, gather, scatter meta

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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.

❌ 1 Failures, 2 Pending

As of commit 6e1d37c:

The following jobs have failed:

• linux-bionic-cuda11.6-py3.10-gcc7-bazel-test / build-and-test

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

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[z-a-f]

Just gonna add some context here :)

https://docs.google.com/document/d/1iiLNwR5ohAsw_ymfnOpDsyF6L9RTUaHMpD8YLw-jxEw/edit

[facebook-github-bot]

@albanD has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[albanD]

@pytorchbot merge -f "Internal diff landed properly"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

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 @albanD.
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.