From 593804dcfe40e2b64afb522d1d1abc6acf180b64 Mon Sep 17 00:00:00 2001 From: AaronStGeorge Date: Wed, 2 Sep 2026 21:32:08 +0000 Subject: [PATCH] ggml-hrx: adapt Loom compile configuration Loom removed the config member from loomc_compile_options_t, breaking the compile-time binding and resolution-policy assignments. The API change lets compilation consume typed configuration modules without retaining text parsing support; this caller's text bindings are already materialized at link time. pr that broke it: https://github.com/ROCm/hrx-system/pull/494 --- ggml/src/ggml-hrx/loom-jit.cpp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/ggml/src/ggml-hrx/loom-jit.cpp b/ggml/src/ggml-hrx/loom-jit.cpp index 452d031024d..4277f03a030 100644 --- a/ggml/src/ggml-hrx/loom-jit.cpp +++ b/ggml/src/ggml-hrx/loom-jit.cpp @@ -921,9 +921,7 @@ hrx_status_t ggml_hrx_loom_jit_amdgpu_compile(ggml_hrx_loom_jit_amdgpu * if (options->evaluate_launch_config) { compile_options.artifact_flags |= LOOMC_COMPILE_ARTIFACT_FLAG_LAUNCH_CONFIG; } - compile_options.config.bindings = config_bindings.get(); - compile_options.config.binding_count = options->config_binding_count; - compile_options.config.flags = LOOMC_CONFIG_POLICY_FLAG_REQUIRE_RESOLVED; + compile_options.config_flags = LOOMC_CONFIG_POLICY_FLAG_REQUIRE_RESOLVED; status = loomc_compile_module(jit->compiler, workspace.get(), jit->pass_program, module.get(), &compile_options, loomc_allocator_system(), result.out()); if (!loomc_status_is_ok(status)) {