pytorch - 💡(How to fix) Fix RocM: Assumed realtime clock rate [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#181499Fetched 2026-04-26 05:05:32
View on GitHub
Comments
1
Participants
2
Timeline
63
Reactions
0
Author
Timeline (top)
mentioned ×28subscribed ×28labeled ×5added_to_project_v2 ×1

Error Message

[302/895] Building HIPCC object caffe2/CMakeFiles/torch_hip.dir/__/aten/src/ATen/native/hip/torch_hip_generated_group_norm_kernel.hip.o In file included from /home/ste/code/pytorch/aten/src/ATen/native/hip/group_norm_kernel.hip:8: In file included from /opt/rocm/include/thrust/tuple.h:33: In file included from /opt/rocm/include/thrust/detail/config.h:22: In file included from /opt/rocm/include/thrust/detail/config/config.h:23: In file included from /opt/rocm/include/thrust/detail/config/libcxx.h:44: In file included from /opt/rocm/include/cuda/std/version:31: In file included from /opt/rocm/include/cuda/std/detail/__config:67: /opt/rocm/include/cuda/std/detail/libcxx/include/__config:371:12: warning: Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly! [-W#warnings] 371 | # warning Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly! | ^ 1 warning generated when compiling for gfx1100. ninja: build stopped: subcommand failed. error: subprocess-exited-with-error

× Building editable for torch (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> No available output.

note: This error originates from a subprocess, and is likely not a problem with pip. full command: /home/ste/code/pytorch/.venv/bin/python /home/ste/code/pytorch/.venv/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_editable /tmp/tmp5ec9a96l cwd: /home/ste/code/pytorch Building editable for torch (pyproject.toml) ... error ERROR: Failed building editable for torch Failed to build torch error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects ╰─> torch

Code Example

Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly!

---

USE_CUDA=0
USE_XPU=0
USE_ROCM=1
PYTORCH_ROCM_ARCH=gfx1100  # I also tried gfx1103
HSA_OVERRIDE_GFX_VERSION=11.0.0

---

[302/895] Building HIPCC object caffe2/CMakeFiles/torch_hip.dir/__/aten/src/ATen/native/hip/torch_hip_generated_group_norm_kernel.hip.o
  In file included from /home/ste/code/pytorch/aten/src/ATen/native/hip/group_norm_kernel.hip:8:
  In file included from /opt/rocm/include/thrust/tuple.h:33:
  In file included from /opt/rocm/include/thrust/detail/config.h:22:
  In file included from /opt/rocm/include/thrust/detail/config/config.h:23:
  In file included from /opt/rocm/include/thrust/detail/config/libcxx.h:44:
  In file included from /opt/rocm/include/cuda/std/version:31:
  In file included from /opt/rocm/include/cuda/std/detail/__config:67:
  /opt/rocm/include/cuda/std/detail/libcxx/include/__config:371:12: warning: Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly! [-W#warnings]
    371 | #          warning Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly!
        |            ^
  1 warning generated when compiling for gfx1100.
  ninja: build stopped: subcommand failed.
  error: subprocess-exited-with-error
  
  × Building editable for torch (pyproject.toml) did not run successfully.
   exit code: 1
  ╰─> No available output.
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  full command: /home/ste/code/pytorch/.venv/bin/python /home/ste/code/pytorch/.venv/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_editable /tmp/tmp5ec9a96l
  cwd: /home/ste/code/pytorch
  Building editable for torch (pyproject.toml) ... error
  ERROR: Failed building editable for torch
Failed to build torch
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> torch
RAW_BUFFERClick to expand / collapse

🐛 Describe the bug

I have an AMD gfx1103 GPU which is not supported by the standard RocM release. I was able, however, to compile TheRock 7.12 to support it.

rocminfo shows the card as gfx1100.

Since TheRock is not supported by PyTorch, I am compiling it from source.

During compilation, I run into this error (see details in error area below):

Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly!

My env variables:

USE_CUDA=0
USE_XPU=0
USE_ROCM=1
PYTORCH_ROCM_ARCH=gfx1100  # I also tried gfx1103
HSA_OVERRIDE_GFX_VERSION=11.0.0

I tried compiling the PyTorch HEAD as well as the v2.11.0 release tag. Both give me the same result.

Is there something else I need to set up to pass the correct clock rate? Can I temporarily have the warning not stop compilation, just to test if the process otherwise works?

Error logs

[repeated many times]

  [302/895] Building HIPCC object caffe2/CMakeFiles/torch_hip.dir/__/aten/src/ATen/native/hip/torch_hip_generated_group_norm_kernel.hip.o
  In file included from /home/ste/code/pytorch/aten/src/ATen/native/hip/group_norm_kernel.hip:8:
  In file included from /opt/rocm/include/thrust/tuple.h:33:
  In file included from /opt/rocm/include/thrust/detail/config.h:22:
  In file included from /opt/rocm/include/thrust/detail/config/config.h:23:
  In file included from /opt/rocm/include/thrust/detail/config/libcxx.h:44:
  In file included from /opt/rocm/include/cuda/std/version:31:
  In file included from /opt/rocm/include/cuda/std/detail/__config:67:
  /opt/rocm/include/cuda/std/detail/libcxx/include/__config:371:12: warning: Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly! [-W#warnings]
    371 | #          warning Assuming 100 MHz realtime clock rate (TSC) for gfx1100/gfx1101 (according to the RDNA3 ISA). Timing-related APIs (e.g., chrono) or sleep instructions may behave incorrectly!
        |            ^
  1 warning generated when compiling for gfx1100.
  ninja: build stopped: subcommand failed.
  error: subprocess-exited-with-error
  
  × Building editable for torch (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> No available output.
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  full command: /home/ste/code/pytorch/.venv/bin/python /home/ste/code/pytorch/.venv/lib/python3.14/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py build_editable /tmp/tmp5ec9a96l
  cwd: /home/ste/code/pytorch
  Building editable for torch (pyproject.toml) ... error
  ERROR: Failed building editable for torch
Failed to build torch
error: failed-wheel-build-for-install

× Failed to build installable wheels for some pyproject.toml based projects
╰─> torch

Versions

  • HEAD at 68535d0c7ffbfb8e2094315241b9b84f364734ad
  • v2.11.0 at 70d99e998b4955e0049d13a98d77ae1b14db1f45

cc @malfet @seemethere @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @jataylo @hongxiayang @naromero77amd @pragupta @jerrymannil @xinyazhang @chauhang @penguinwu

extent analysis

TL;DR

The compilation of PyTorch from source for an AMD gfx1103 GPU is failing due to an assumed 100 MHz realtime clock rate warning that stops the build process.

Guidance

  • The warning is related to the gfx1100/gfx1101 GPU architecture, and the build process is treating the gfx1103 as a gfx1100.
  • To temporarily bypass the warning and continue the compilation, you can try setting the WARNINGS_AS_ERRORS environment variable to OFF or modifying the CMake configuration to treat warnings as non-fatal errors.
  • Verify that the PYTORCH_ROCM_ARCH environment variable is correctly set to gfx1103 to ensure the build process is using the correct architecture.
  • Consider modifying the HSA_OVERRIDE_GFX_VERSION environment variable to a version that supports the gfx1103 GPU, if available.

Example

No code snippet is provided as the issue is related to environment variables and build configuration.

Notes

The provided solution is a temporary workaround to bypass the warning and continue the compilation. The actual fix may require updating the ROCm or PyTorch versions to support the gfx1103 GPU architecture.

Recommendation

Apply workaround: temporarily bypass the warning by setting WARNINGS_AS_ERRORS to OFF or modifying the CMake configuration, as the issue is likely due to the assumed clock rate and not a critical error.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

pytorch - 💡(How to fix) Fix RocM: Assumed realtime clock rate [1 comments, 2 participants]