commit 8d8ed574b796ad4ec3fe4b1dcc0c360d3ce3ce7a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 03:46:47 2026 +0200

dev-debug/rocr-debug-agent: trim 10.0.0 comment prose

commit 6c6f809e018d5167ab9a5aa32f3376c4002d064b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 31 00:42:38 2026 +0200

dev-debug/rocr-debug-agent: new package, add 10.0.0

Second of the ROCm debugging/profiling components ::gentoo does not carry.
Loaded into an application through HSA_TOOLS_LIB, it prints wavefront state,
the faulting instruction and a disassembly of the surrounding code object when
the GPU takes a memory fault, then leaves the process for a debugger. It reads
that state through the same amd-dbgapi surface dev-debug/gdb already consumes
via dev-libs/rocdbgapi, which is why it lands in dev-debug rather than dev-libs.

Versioned by the ROCm release rather than upstream's project(VERSION 2.1.0),
matching the rest of the stack; the soname still carries the real 2.

Dependencies were taken from the built artifact rather than from the CMake
text alone -- objdump -p on librocm-debug-agent.so.2.1.0 reports exactly
librocm-dbgapi.so.0, libhsa-runtime64.so.1, libelf.so.1 and libdw.so.1, so
dev-libs/elfutils covers both of upstream's separate libdw and libelf lookups
and there is nothing undeclared.

-Werror is dropped, guarded with grep-or-die. A library compiled against three
external header sets with -Werror breaks on an unrelated upstream deprecation
sooner or later, and sed exits 0 on no-match so an unguarded expression would
quietly stop doing anything.

dev-debug is a new category for this overlay. No profiles/categories entry is
needed: the overlay declares masters = gentoo and dev-debug already exists
there.

Build-verified and merged on haarmek. Run-verified as far as is sensible
without deliberately faulting the GPU: the library exports exactly the HSA
tool interface (OnLoad/OnUnload), and HSA_TOOLS_LIB=librocm-debug-agent.so.2
rocminfo loads it, enumerates the gfx1150 agent normally and exits 0 -- so it
is loadable, ABI-compatible with the installed HSA runtime, and does not
disturb ordinary execution.