AMD Releases HIPRT 3.2 Library Update Adding Medusa APU Support
The latest version of AMD’s HIP ray-tracing library adds support for the Medusa APU and serves as the first update to the software since the start of 2026.
Key points
- AMD has released version 3.2 of its HIPRT ray-tracing library.
- The update introduces support for the Medusa APU hardware.
- This release marks the first change to the library since early 2026.
AMD has released version 3.2 of its HIPRT ray-tracing library, introducing support for the company’s Medusa APU. According to Phoronix, this release serves as the first update to the HIPRT software since the beginning of 2026. The update adds specific hardware support within the AMD ecosystem.
The HIPRT library provides ray-tracing acceleration capabilities for developers working with AMD graphics hardware. By adding support for the Medusa APU, AMD ensures that developers can utilize ray-tracing features on this specific accelerated processing unit. This expansion allows for broader application of real-time ray-tracing technologies across different device classes supported by the vendor.
Software Context and Release History
This release is the first update to the HIPRT library since the beginning of 2026, according to Phoronix. The source material does not specify the content of any updates prior to this release or the exact duration of the gap beyond stating it is the first since the year started. The release cycle is defined by this specific milestone in the library's development timeline.
The Medusa APU represents a segment of AMD’s broader hardware portfolio. Integrating ray-tracing support directly into the HIPRT library is the primary function of this update. This standardization is part of the library's role in supporting AMD's hardware stack.
Who Is Affected
Developers creating applications that rely on AMD’s HIP ecosystem are the primary audience for this update. Teams building games, professional visualization tools, or scientific computing applications may need to update their dependencies to ensure compatibility with the Medusa APU. Users of the Medusa APU who run applications leveraging HIPRT will see improved functionality through this library update.
The update does not affect users of other graphics architectures or those not utilizing ray-tracing features. Since HIPRT is specific to AMD’s hardware stack, developers working with NVIDIA or Intel solutions are not impacted by this release. The change is confined to the AMD software development kit environment.
What should you do?
System administrators and developers should monitor their project dependencies for compatibility with HIPRT 3.2. Testing applications against the new library version is recommended before deploying to production environments that include Medusa APUs. Organizations should verify that their build systems can accommodate the updated library without breaking existing functionality.
What to do and how to stay safe: AMD
- Review application dependencies to determine if HIPRT libraries are currently in use.
- Test software builds against the new HIPRT 3.2 version to ensure stability.
- Monitor vendor documentation for any additional hardware support details.
- Update development environments to include the latest AMD graphics drivers.
Step-by-step guide: Mobile Device Security: How to Protect Data Beyond Passwords
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What does HIPRT 3.2 add?
It adds support for the Medusa APU and is the first update since early 2026.
Is this a security fix?
The source material does not mention security vulnerabilities or fixes.
Who released this update?
AMD released the update, as reported by Phoronix.
