Make torch/csrc/utils.h to be device-agnostic

[FFFrog]

Stack from ghstack (oldest at bottom):

• Remove the unnecessary cuda/Tensor.cpp #152522
• -> Make torch/csrc/utils.h to be device-agnostic #152521
• Remove unnecessary __STDC_FORMAT_MACROS macro #152513
• Remove unnecessary condition compilation macro #152512

torch/csrc/utils.h should be device-independent. Currently, it contains CUDA-related implementations, which indirectly causes the failure of ROCm testing (The reason is that the ROCm test environment shouldn`t expose HIP-related header files, which causes the JIT compilation to fail during testing)

Therefore, move CUDA-related implementations to torch/csrc/cuda/utils.h.

Question:
This change may introduce BC-breack.
I searched for this function globally on github and I think the impact is very small.

[pytorch-bot]

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• CI workflows being skipped on PR

❌ 1 New Failure, 1 Unrelated Failure

As of commit 2d843b5 with merge base 59a8aa1 ():

NEW FAILURE - The following job has failed:

• rocm / linux-focal-rocm-py3.10 / test (default, 2, 6, linux.rocm.gpu.2) (gh)
  dynamo/test_logging.py::LoggingTests::test_inductor_info

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

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

• trunk / macos-py3-arm64 / test (default, 2, 3, macos-m1-stable) (gh) (trunk failure)
  dynamo/test_logging.py::LoggingTests::test_inductor_info

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

[FFFrog]

@pytorchbot label "topic: not user facing"

[albanD]

There is a major difference between "no breakage" and "the impact is very small". We should be careful to aim for "no breakage" in general. And treat everything else as BC-breaking.
From the github search, I see no use outside of pytorch codebase or clones. So sounds good!

[FFFrog]

There is a major difference between "no breakage" and "the impact is very small". We should be careful to aim for "no breakage" in general. And treat everything else as BC-breaking. From the github search, I see no use outside of pytorch codebase or clones. So sounds good!

Thank you a lot.

[FFFrog]

@pytorchbot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 1 checks: rocm / linux-focal-rocm-py3.10 / test (default, 2, 6, linux.rocm.gpu.2)

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

[pytorchmergebot]

Starting merge as part of PR stack under #152522