From e163e22498142c28f2deb368114dbddc2b0a0418 Mon Sep 17 00:00:00 2001 From: Julia Jiang Date: Fri, 8 Aug 2025 14:33:38 -0400 Subject: [PATCH] SWDEV-538999 - Make correction in porting guid for launch_bounds --- docs/how-to/hip_porting_guide.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/how-to/hip_porting_guide.rst b/docs/how-to/hip_porting_guide.rst index 136084f66b..ea74552353 100644 --- a/docs/how-to/hip_porting_guide.rst +++ b/docs/how-to/hip_porting_guide.rst @@ -624,13 +624,12 @@ implementation, however it uses different parameters: The first parameter is the same as HIP's implementation, but ``MIN_BLOCKS_PER_MULTIPROCESSOR`` must be converted to ``MIN_WARPS_PER_EXECUTION``, which uses warps and execution units rather than -blocks and multiprocessors. This conversion is performed automatically by -:doc:`HIPIFY `, or can be done manually with the following +blocks and multiprocessors. This conversion can be done manually with the following equation. .. code-block:: cpp - MIN_WARPS_PER_EXECUTION_UNIT = (MIN_BLOCKS_PER_MULTIPROCESSOR * MAX_THREADS_PER_BLOCK) / warpSize + MIN_WARPS_PER_EXECUTION_UNIT = (MIN_BLOCKS_PER_MULTIPROCESSOR * MAX_THREADS_PER_BLOCK) / (warpSize * NUM_EUS_PER_CU) Directly controlling the warps per execution unit makes it easier to reason about the occupancy, unlike with blocks, where the occupancy depends on the