commit c5f55df8de638e5e56fde1ac664ce0f716b0f668
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Sep 11 23:50:33 2026 +0200

dev-python/triton: disable LTO in 3.7.1

The AMD and NVIDIA backend archives expose conflicting global
definitions when combined into libtriton. GCC diagnoses them during LTO,
and upstream's -Werror turns the diagnostics into a link failure.

Filter LTO until upstream makes the combined link ODR-clean. Upstream
tests remain restricted because they require accelerator hardware.

Bug: https://github.com/istitov/stuff/issues/286

commit 6498fd2dbc9f365ca48b994f85e9fcfdc7890eed
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Sep 10 03:21:01 2026 +0200

dev-python/triton: trim 3.7.1 comment prose

commit f913e6eecd6f49f2e91b4cf61e0836c34daf7f05
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Sep 9 17:55:22 2026 +0200

dev-python/triton: symlink the CUDA tools the offline build omits

The CUDA backend had no ptxas, so the package compiled, installed and
imported cleanly and then died at the first CUDA JIT with "Cannot find
ptxas".

TRITON_OFFLINE_BUILD=1 suppresses upstream's download of the NVIDIA tools
and the source tarball carries none, so nothing ever placed them in
backends/nvidia/bin. knobs.py resolves them through env_nvidia_tool, which
tries $TRITON_<TOOL>_PATH and then that directory and raises RuntimeError;
there is no PATH fallback, so the toolkit already being on PATH through
env.d does not help.

Symlink ptxas, cuobjdump and nvdisasm to the toolkit and depend on it.
ptxas-blackwell has no toolkit counterpart, so sm_100 and later still need
TRITON_PTXAS_BLACKWELL_PATH set by hand.

The binary wheel bundles the NVIDIA tools itself, so only this provider was
affected -- which is why the gap survived: nothing had ever selected it.
Found by build-checking through install and reading the staged image rather
than the sources.

commit 00a30854274bd1059070667f705f77b5f84caeb2
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Sep 9 17:16:47 2026 +0200

dev-python/triton: declare the bundled LLVM and HSA licences

LICENSE="MIT" covered only the Triton half of what this package ships.

The ebuild fetches upstream's prebuilt LLVM alongside the Triton sources,
and that code reaches the installed tree in two forms: statically linked
into triton/_C/libtriton.so, which is 162 MiB, resolves no external libLLVM
through ldd and exports llvm symbols of its own, and copied verbatim as
triton/FileCheck. The AMD backend additionally installs six HSA headers
under triton/backends/amd/include/hsa carrying the University of
Illinois/NCSA licence, and python_install does not remove them.

Every term is cumulative rather than an any-of choice. Read off the staged
image rather than inferred from SRC_URI.

commit f0329e072a3280b7a9a50a91a4fc3693d1fd3efb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 23 12:42:34 2026 +0200

dev-python/triton: block triton-bin

commit 5f9a8189f547c108baf0c909d5b53b926160adc2
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Aug 23 11:00:41 2026 +0200

dev-python/triton: new package

GPU-kernel compiler built from source against upstream's pinned LLVM
(commit 1f126a6d, prestaged via a SRC_URI blob with TRITON_OFFLINE_BUILD=1).
Several LLVM translation units need multiple GiB each, so MAX_JOBS is
capped at 4 to avoid OOM.