Use a different build directory

Oct 13, 2025 by pynkocean.com 119 views

The Litterbug of HIPCC: A Troublesome Issue in ROCm Containers

In the world of high-performance computing, the ROCm (Radeon Open Compute) platform has emerged as a powerful tool for developers and researchers. However, like any complex system, it is not immune to issues and bugs. One such problem that has been reported by users is the tendency of HIPCC (High-Performance Compiler and Coder) to leave behind a trail of files in the /tmp directory, even after a successful build. In this article, we will delve into the details of this issue, explore the possible causes, and provide a step-by-step guide to reproduce and troubleshoot the problem.

The issue at hand is that HIPCC, when used in a ROCm container, leaves behind a large number of files in the /tmp directory. This can be a significant problem, especially when working with large projects or in environments where disk space is limited. To illustrate this issue, let's consider a simple test case.

rm -rf tmp-test
mkdir -p tmp-test
export TMPDIR="$(realpath tmp-test)"
export TEMPDIR="$(realpath tmp-test)"
ls -lR "${TMPDIR}" | wc -l
make
ls -lR "${TMPDIR}" | wc -l

In this example, we first create a temporary directory tmp-test and set the TMPDIR and TEMPDIR environment variables to point to this directory. We then list the contents of the directory using ls -lR and count the number of files using wc -l. After running the make command, we repeat the same process to see if any new files have been created.

The issue has been reported to occur on the rocm/dev-ubuntu-22.04:6.33-complete container, which is based on Ubuntu 22.04. This container is a popular choice for developers and researchers working with ROCm.

Interestingly, the issue does not seem to be dependent on the type of CPU or GPU being used. This suggests that the problem may be related to the HIPCC compiler or the ROCm platform itself, rather than the specific hardware configuration.

The ROCm version being used is 6.3.3, which is a relatively recent release. This suggests that the issue may be a bug or a known limitation in the current version of ROCm.

The issue specifically affects the HIPCC component of ROCm. HIPCC is a high-performance compiler and coder that is designed to work with the ROCm platform.

To reproduce the issue, follow these steps:

Create a temporary directory tmp-test and set the TMPDIR and TEMPDIR environment variables to point to this directory.
Run the make command to build your project.
List the contents of the directory using ls -lR and count the number of files using wc -l.
Repeat steps 2-3 to see if any new files have been created.

If you are experiencing this issue, there are a few things you can try to troubleshoot and potentially resolve the problem:

Check the ROCm logs: The ROCm platform generates logs that can provide valuable information about what is happening during the build process. Check the logs to see if there are any errors or warnings that may be related to the issue.
Use a different build directory: Try building your project in a different directory to see if the issue persists.
Update ROCm: If you are using an older version of ROCm, try updating to the latest version to see if the issue has been fixed.
Contact ROCm support: If none of the above steps resolve the issue, contact ROCm support for further assistance.

In conclusion, the issue of HIPCC leaving behind files in the /tmp directory is a real problem that can be frustrating for developers and researchers working with ROCm. By understanding the possible causes and following the steps outlined in this article, you can troubleshoot and potentially resolve the issue. If you are experiencing this problem, we encourage you to try the troubleshooting steps outlined above and contact ROCm support if you need further assistance.
HIPCC Litterbug Q&A: Frequently Asked Questions

In our previous article, we explored the issue of HIPCC leaving behind files in the /tmp directory, even after a successful build. In this article, we will answer some of the most frequently asked questions about this issue, providing additional insights and guidance for developers and researchers working with ROCm.

Q: What is the HIPCC litterbug?

A: The HIPCC litterbug refers to the issue where HIPCC, a high-performance compiler and coder, leaves behind a large number of files in the /tmp directory, even after a successful build.

Q: Why is this a problem?

A: This issue can be a significant problem, especially when working with large projects or in environments where disk space is limited. The files left behind by HIPCC can consume a large amount of disk space, causing performance issues and potentially leading to data loss.

Q: Is this issue specific to ROCm?

A: No, this issue is not specific to ROCm. However, it is more pronounced in ROCm containers, where the /tmp directory is often used as a temporary storage area.

Q: Can I prevent HIPCC from leaving behind files?

A: Yes, there are several ways to prevent HIPCC from leaving behind files. One approach is to use a different build directory, such as a directory on a different disk or a network-mounted directory. Another approach is to use a tool like tmpreaper to automatically clean up the /tmp directory.

Q: How can I troubleshoot this issue?

A: To troubleshoot this issue, you can try the following steps:

Check the ROCm logs: The ROCm platform generates logs that can provide valuable information about what is happening during the build process. Check the logs to see if there are any errors or warnings that may be related to the issue.
Use a different build directory: Try building your project in a different directory to see if the issue persists.
Update ROCm: If you are using an older version of ROCm, try updating to the latest version to see if the issue has been fixed.
Contact ROCm support: If none of the above steps resolve the issue, contact ROCm support for further assistance.

Q: Is this issue fixed in the latest version of ROCm?

A: The issue of HIPCC leaving behind files in the /tmp directory is still present in the latest version of ROCm. However, the ROCm team is working to resolve this issue in future releases.

Q: Can I report this issue to the ROCm team?

A: Yes, you can report this issue to the ROCm team using the ROCm issue tracker. Please provide as much detail as possible, including the steps to reproduce the issue and any relevant logs or output.

In conclusion, the HIPCC litterbug is a real issue that can be frustrating for developers and researchers working with ROCm. By understanding the possible causes and following the steps outlined in this article, you can troubleshoot and potentially resolve the issue. If you are experiencing this problem, we encourage you to try the troubleshooting steps outlined above and contact ROCm support if you need further assistance.