commit f6bc6f74effa29a708b6d2db20041c9ae4227b3a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Aug 14 20:19:16 2026 +0200

dev-python/tilelang: honor CUDAHOSTCXX during JIT

TileLang passes an explicit host compiler to nvcc, so NVCC_PREPEND_FLAGS cannot
override an unsupported system compiler. Prefer CUDAHOSTCXX in the runtime compiler
helper and document that effective control.

commit 71061964d300f5db66a5e75dce8bc427434de22d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Aug 14 10:24:04 2026 +0200

dev-python/tilelang: enforce build dependency floors

The 0.1.13 source requires CMake 3.26.1 through its scikit-build configuration and Z3
4.13.0 through its project metadata. Express both floors so older versions cannot
satisfy the build dependencies.

commit dc01f2f074c02c7d0f24dae16d1238b96198a02a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Aug 14 09:06:19 2026 +0200

dev-python/tilelang: honor CUDAHOSTCXX for runtime JIT

TileLang unconditionally adds an nvcc compiler-bindir flag derived from CXX or PATH,
overriding NVCC_PREPEND_FLAGS and selecting compilers rejected by CUDA 13. Prefer
CUDAHOSTCXX explicitly and retain a compatible GNU C++ compiler for runtime kernel
generation.

commit 99dd7c7c99e8f35ba76db237290776b08f71f3be
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Aug 13 19:18:59 2026 +0200

dev-python/tilelang: drop 0.1.11

The retained later 0.1 releases provide rollback coverage without carrying this
superseded version.

commit f430fa51c1c55e751dd408a0bbab82ff8583aaff
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Aug 12 01:52:33 2026 +0200

dev-python/tilelang: add 0.1.12 for vllm 0.27.1 cuda

commit 84463cae405576121dbfc32036212999f451b1a9
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Aug 5 10:55:00 2026 +0200

dev-python/tilelang: date the z3-solver cap rationale

Stamp the tested-version cap note; the in-tree z3 (4.16.0/5.0.0) is newer than
upstream's <4.15.5 ceiling.

commit abc016550c4f45d53bb54d7e3a12d256ed71a7b0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 18:05:08 2026 +0200

dev-python/tilelang: fix backend and FFI integration in 0.1.13

Model CUDA and ROCm as exclusive backends, select supported toolchains, and
repair installed library paths. Pin the exact apache-tvm-ffi release the
ABI-symlink build links against, and leave compiler caching to Portage.

commit fa89282afb1c9d66aeec897fb2293dbf67fafd6a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 18:05:00 2026 +0200

dev-python/tilelang: fix backend and FFI integration in 0.1.11

Model CUDA and ROCm as exclusive backends, select supported toolchains, and
repair installed library paths. Follow upstream's compatible FFI range and
leave compiler caching to Portage.

commit b5bdc1beb8b0e91d22b6640ac07cc368fab2323a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 18:04:51 2026 +0200

dev-python/tilelang: fix backend and FFI integration in 0.1.10

Model CUDA and ROCm as exclusive backends, select supported toolchains, and
repair installed library paths. Retain the bundled 0.1.11 header snapshot,
follow upstream's compatible FFI range, and leave caching to Portage.

commit a050ecabea99aca40e7cfb3dc55410e8475950af
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 18:04:43 2026 +0200

dev-python/tilelang: fix backend and FFI integration in 0.1.9

Model CUDA and ROCm as exclusive backends, select supported toolchains, and
repair installed library paths. Keep the bundled FFI headers, follow upstream's
compatible FFI range, and leave compiler caching to Portage.

commit b9958b40ff462a8fa723391c914a05abc2d78623
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 14:51:21 2026 +0200

dev-python/tilelang: restore 0.1.9 and 0.1.10

Retained vLLM releases still require these exact backend versions for CUDA and ROCm.
Restore the previously verified ebuilds so their dependency branches remain solvable.

commit 83f5e064f233f60d87053765ab5eeb272f989aae
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 09:46:33 2026 +0200

dev-python/tilelang: drop 0.1.9, 0.1.10, 0.1.12

0.1.12 caps <dev-python/apache-tvm-ffi-0.1.12, but the tree no longer
carries a tvm-ffi below 0.1.12, so that bound no longer solves. 0.1.9
and 0.1.10 were already past the last-two retention window. Keep 0.1.11
(open tvm-ffi dep) alongside the new 0.1.13 for rollback.

commit 9fb7715fb55030f93406859c3104cd749cc6b89f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 09:46:02 2026 +0200

dev-python/tilelang: add 0.1.13

commit ba297f2bb98e5b1020078236fa0a2508549c8998
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Jul 10 14:22:22 2026 +0200

dev-python/tilelang: add 0.1.12

commit 255d2b80fa6d8a5dd918c486b5d25b8c60e9d2a6
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 9 01:08:43 2026 +0200

dev-python/tilelang: restore 0.1.9

dev-python/vllm (0.21.0, 0.22.1) pins ~dev-python/tilelang-0.1.9; dropping
0.1.9 left that dependency unsatisfiable. Keep it while vllm requires the
exact version.

commit 8b03f9b1092c6157223d84122867366a503b896b
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jun 8 12:58:45 2026 +0200

dev-python/tilelang: drop 0.1.9

commit 2d960f92899c50884f3e7ac2abdefd6968e14065
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jun 8 12:58:31 2026 +0200

dev-python/tilelang: add 0.1.11

libtvm_runtime.so/libtilelang.so call CUDA driver symbols but Gentoo's
--as-needed strips the libcuda stub from DT_NEEDED despite
TILELANG_USE_CUDA_STUBS=OFF; with -z now this fails 'import tilelang' at
dlopen. python_install_all re-adds libcuda.so.1 via patchelf. pkg_postinst
documents the runtime-JIT NVCC_PREPEND_FLAGS=-ccbin gcc-15 requirement on
CUDA 13.x. Verified import + sm_86 GPU kernel.

commit 00e82f29e8e5359d45fd0c4498e2f881668e06ce
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon May 25 14:00:21 2026 +0200

dev-python/tilelang: add 0.1.10

Patch bump from 0.1.9. Upstream tightened apache-tvm-ffi pin from
~=0.1.0,>=0.1.2 to ~=0.1.0,>=0.1.10; mirror that with a >=0.1.10
floor on the python_gen_cond_dep entry (we already ship 0.1.11 in
the overlay so resolution stays clean). Other pyproject.toml deps
unchanged. Build-verified with python3_13 single-impl + the
existing CMAKE_CUDA_HOST_COMPILER / TILELANG_USE_CUDA_STUBS workarounds;
all four dated rationale comments re-verified against 0.1.10.

commit 51472bd93965ef04435f1165226d7a499e1bc72f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 13 14:42:59 2026 +0200

dev-python/tilelang: drop stale python3_11 conditional

python_single_target_python3_11 was removed from PYTHON_COMPAT in the
python3_11 sweep but the torch-c-dlpack-ext conditional block was not
cleaned up, causing an UnstatedIuse pkgcheck error.

commit 5458d487801025adc249579494ecf1bb7eb68c52
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 13 14:35:35 2026 +0200

dev-python/tilelang: disable py3.11

commit 738368c3910b766e9fd40e870d6d78a5ceba313f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun May 10 16:13:17 2026 +0200

dev-python/tilelang: fix z3 dep — use $

sci-mathematics/z3 is python-single-r1 (single-impl). The earlier
DISTUTILS_SINGLE_IMPL conversion left z3 inside python_gen_cond_dep
with [python,$], which silently auto-satisfies via
[X(-)?] when z3 doesn't have python_targets_* in IUSE. Move it out of
the multi-impl wrap and use [python,$] so the
Python-target match between tilelang and z3 is actually enforced.

commit 6ad25de09e790db9d83139a3d5611d32b6c04769
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun May 10 15:28:12 2026 +0200

dev-python/tilelang: switch to DISTUTILS_SINGLE_IMPL

sci-ml/pytorch is SINGLE_IMPL, and the existing python_targets_python3_*?
guards on the now-single-impl dev-python/torch-c-dlpack-ext need to flip
to python_single_target_python3_*?. Multi-impl helpers (apache-tvm-ffi,
cloudpickle, ml-dtypes, etc.) move into python_gen_cond_dep.

commit 655ba501a783d05d1463c4978bc50efbe0a409e3
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu May 7 18:25:53 2026 +0200

dev-python/tilelang: new package, 0.1.9

Tier 4 of the vllm CUDA target packaging cycle. Tile-level programming
language for high-performance ML kernels — used by flashinfer-python's
fused-attention paths and (via apache-tvm-ffi) by quack-kernels.

Build is scikit-build-core + a vendored full TVM source tree (407 MiB
under 3rdparty/tvm), plus vendored CUTLASS C++ and Composable-Kernel
headers. ~677 ninja steps; on this 24-thread / 31 GiB host the full
build runs ~10 min once unblocked.

Three ebuild-side fixes were needed to land:

* z3 lookup. Upstream's bundled cmake/pypi-z3/FindZ3.cmake searches
ONLY inside the PyPI z3-solver wheel's site-packages layout
(NO_DEFAULT_PATH). On Gentoo the headers + libz3 live at standard
/usr/include + /usr/lib64 paths. Pre-setting Z3_INCLUDE_DIR and
Z3_LIBRARY via DISTUTILS_ARGS short-circuits find_path /
find_library and lets the imported z3::libz3 target build cleanly
against ::gentoo's z3.

* nvcc host compiler. CUDA 13.2's crt/host_config.h hard-#errors when
__GNUC__ > 15, but this host's active gcc is 16. Pinning nvcc's
host compiler to /usr/bin/x86_64-pc-linux-gnu-g++-15 (slot 2 from
gcc-config) via -DCMAKE_CUDA_HOST_COMPILER and CUDAHOSTCXX keeps
the system slot at 16 while the CUDA toolchain stays in band.
Likely affects every other CUDA-source consumer in this stack.

* CUDA stub linkage. TILELANG_USE_CUDA_STUBS defaults ON and links
libtvm.so against tilelang's own libcudart_stub / libnvrtc_stub
for "portable wheel" lazy resolution. But there is no driver-API
stub, so direct calls to cuDeviceGetName etc. become undefined-
symbol at import. Turning the option OFF makes the build NEEDED-
link libtvm.so directly against /opt/cuda's stubs/libcuda.so /
libcudart.so / libnvrtc.so — the SONAMEs resolve to the real
driver+runtime libs at runtime via /etc/ld.so.cache. We don't
ship portable wheels, so the loss-of-portability is moot.

Z3-solver pin (<4.15.5) is intentionally NOT honored — ::gentoo only
carries z3-4.16.0; the cap reads as conservative ("tested up to here")
and tilelang imports + initializes cleanly against 4.16. Will revisit
if a runtime test surfaces a real incompatibility.

Accepting the NonsolvableDepsInStable false positive from
sci-mathematics/z3 / sci-ml/pytorch keyword stacks (same shape as
xgrammar etc.).