[Distributed/Profiler] Fix input/output dimension overflow

[sraikund16]

Summary: When using ParamCommsDebugInfo, the input elements and output elements are stored in int instead of int64_t

Test Plan: Run HTA with new outputted values and make sure overflow does not occur

Reviewed By: fengxizhou

Differential Revision: D61728747

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 the bot commands wiki or our office hours

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit 8a038dc with merge base 74a9001 ():

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• trunk / linux-focal-rocm6.1-py3.8 / test (default, 1, 2, linux.rocm.gpu) (gh) (trunk failure)
  inductor/test_torchinductor.py::CpuTests::test_mutable_custom_op_fixed_layout2_cpu

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D61728747

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D61728747

[fengxizhou]

This PR resolves the outNelems overflow issue for collective gather operator when group_size is large. Changing the data type from int32_t to int64_t can solve the problem and will not affect other component. In my opinion, it's safe to land.

[facebook-github-bot]

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

[pytorch-bot]

This PR needs to be approved by an authorized maintainer before merge.

[jeanschmidt]

@pytorchbot merge -f 'landed internally'

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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