<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:arxiv="http://arxiv.org/schemas/atom" xmlns="http://www.w3.org/2005/Atom">
  <id>https://arxiv.org/api/jnafJJ9SUFy+5gTFf2eKvXadLPc</id>
  <title>arXiv Query: search_query=cat:cs.PL AND (all:"domain-specific language" OR all:metaprogramming OR all:"language-oriented" OR all:"compile-time")&amp;id_list=&amp;start=0&amp;max_results=12</title>
  <updated>2026-09-22T15:18:23Z</updated>
  <link href="https://arxiv.org/api/query?search_query=cat:cs.PL+AND+(all:%22domain-specific+language%22+OR+(all:metaprogramming+OR+(all:%22language-oriented%22+OR+all:%22compile-time%22)))&amp;start=0&amp;max_results=12&amp;id_list=" type="application/atom+xml"/>
  <opensearch:itemsPerPage>12</opensearch:itemsPerPage>
  <opensearch:totalResults>655</opensearch:totalResults>
  <opensearch:startIndex>0</opensearch:startIndex>
  <entry>
    <id>http://arxiv.org/abs/2609.24628v1</id>
    <title>Bridging the Vendor Gap: Enabling AMD GPU Support for Awkward Array via ROCm/HIP for the HL-LHC Era</title>
    <updated>2026-09-21T14:11:12Z</updated>
    <link href="https://arxiv.org/abs/2609.24628v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.24628v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>The High-Luminosity LHC (HL-LHC) will demand order-of-magnitude gains in analysis throughput, and increasingly those gains must come from GPUs that are not made by a single vendor. Leadership-class systems such as El Capitan, Frontier and LUMI are built on AMD accelerators, yet the Scikit-HEP analysis stack---and Awkward Array in particular---has grown up CUDA-first. We report on $rawkward$, a Rust-backed kernel engine that adds a ROCm/HIP backend for Awkward Array's nested, jagged, variable-length data structures. Our central finding is that a naive source-level port of CUDA kernels to HIP loses $5$--$10\times$ in performance on irregular kernels, because AMD's $64$-lane wavefronts, higher register pressure and more expensive divergence behave fundamentally differently from NVIDIA's $32$-thread warps. We show that a small, reusable set of optimization patterns---loop flattening, $128$-bit vectorized loads, splitting fused kernels, and profile-guided launch configuration---recovers CUDA-class performance without changing the public API. A Rust macro-and-match dispatch layer keeps a single, backend-agnostic call site while emitting vendor-specific kernel strategies, and the type system enforces buffer-size and lifetime correctness at compile time. On a two-socket AMD Instinct MI210 node we measure GPU speedups from $1.03\times$ (bandwidth-bound $sum$) up to $12.5\times$ ($count$) over $128$ EPYC~7763 CPU cores, and the Rust CPU kernels match or beat on aggregate the incumbent C++ kernels (geometric-mean runtime ratio $0.37\times$ across twelve kernels). We argue that these patterns constitute a practical recipe for performance-portable, vendor-agnostic HEP analysis kernels.</summary>
    <category term="cs.DC" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-21T14:11:12Z</published>
    <arxiv:comment>8 pages, 2 figures</arxiv:comment>
    <arxiv:primary_category term="cs.DC"/>
    <author>
      <name>Ianna Osborne</name>
    </author>
    <author>
      <name>Maxym Naumchyk</name>
    </author>
    <author>
      <name>Tai Sakuma</name>
    </author>
    <author>
      <name>Andres Rios-Tascon</name>
    </author>
    <author>
      <name>Peter Elmer</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.24345v1</id>
    <title>Garlene: Guarded Recursion in Lean</title>
    <updated>2026-09-21T09:40:31Z</updated>
    <link href="https://arxiv.org/abs/2609.24345v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.24345v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>Extending the recursion principles of a formal system is an enticing but dangerous endeavour with a well-documented history of leading to consistency bugs. Nakano's guarded recursion is an elegant, type-based approach to soundly extend type theory with a powerful recursion principle. This makes guarded recursion useful for many applications, from programming with infinite structures such as streams to reasoning about advanced programming language features using synthetic guarded domain theory. Sadly, guarded recursion is not directly supported by any major interactive theorem prover, which leaves users of guarded recursion with unmechanised pen-and-paper proofs or mechanisations that depend on unmaintained theorem provers. In this paper, we present an implementation of guarded recursion as an embedded language in Lean consisting of a simply-typed lambda calculus for definitions and a higher-order logic for reasoning. Using Lean's excellent support for metaprogramming, our language allows users to write guarded recursive definitions in an intuitive syntax and to prove properties about them using a dedicated proof mode. We give our language a presheaf model, which we use to prove the soundness of our language and to allow users to export guarded recursive definitions and their theorems into standard Lean developments. To demonstrate the usefulness of our language, we present several case studies for programming and reasoning with guarded recursion.</summary>
    <category term="cs.LO" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-21T09:40:31Z</published>
    <arxiv:primary_category term="cs.LO"/>
    <author>
      <name>Sergei Stepanenko</name>
    </author>
    <author>
      <name>Patrick Bahr</name>
    </author>
    <author>
      <name>Rasmus Ejlers Møgelberg</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.24252v1</id>
    <title>Iris in Lean</title>
    <updated>2026-09-21T08:17:46Z</updated>
    <link href="https://arxiv.org/abs/2609.24252v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.24252v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>The Iris framework for concurrent separation logic has been widely used for program verification research. An important factor contributing to the framework's adoption is its high-quality mechanization in Rocq. This mechanization uses a number of Rocq features in sophisticated ways, including a carefully constructed algebraic hierarchy for modeling separation logic resources, and a proof mode for embedded separation logic proofs, which combines custom Ltac with extensible typeclasses. The library has been developed for over a decade with dozens of contributors, with an emphasis on modularity and maintainability.
  We explore how Lean features like flexible metaprogramming and quotient types can simplify the design and usage of Iris. Using these features, we provide a novel implementation of the Iris proof mode with improved performance, simplify the handling of equivalences through quotient types, build a variant of Diaframe proof automation, and provide convenience features like automatic construction of Iris fixed points. Building on Lean lets us integrate with the extensive Mathlib library, allowing us to re-use results from this library for program verification tasks that have heavy mathematical dependencies, as we demonstrate with an application to probabilistic program verification.</summary>
    <category term="cs.LO" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-21T08:17:46Z</published>
    <arxiv:primary_category term="cs.LO"/>
    <author>
      <name>Markus de Medeiros</name>
    </author>
    <author>
      <name>Sergei Stepanenko</name>
    </author>
    <author>
      <name>Zongyuan Liu</name>
    </author>
    <author>
      <name>Oliver Soeser</name>
    </author>
    <author>
      <name>Fernando Leal</name>
    </author>
    <author>
      <name>Alvin Tang</name>
    </author>
    <author>
      <name>Max Vistrup</name>
    </author>
    <author>
      <name>Ralf Jung</name>
    </author>
    <author>
      <name>Mario Carneiro</name>
    </author>
    <author>
      <name>Joseph Tassarotti</name>
    </author>
    <author>
      <name>Michael Sammler</name>
    </author>
    <author>
      <name>Lars Birkedal</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.19598v1</id>
    <title>Theories of Mind as Domain-Specific Languages of Thought</title>
    <updated>2026-09-17T02:26:27Z</updated>
    <link href="https://arxiv.org/abs/2609.19598v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.19598v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>What kind of thing is a ``theory of mind''? We propose to formalize theories of mind as domain-specialized programming languages, which can be used to reason about the mental states of other agents. Our proposal builds on the longstanding idea that thinking is akin to programming in an internal ``language of thought.'' But rather than positing a single general-purpose language for all of thought, we posit a collection of domain-specific languages of thought, whose respective syntaxes and semantices encode the theories of various domains. We make this idea concrete in the domain of intuitive psychology using a real-world programming language called memo, which is specialized for theory-of-mind reasoning via domain-specialized syntactic constructs like ``knows,'' ``wants,'' and ``thinks.'' In our view, using one's theory-of-mind to think about a social situation is analogous to using memo to write a program that models that situation. Through a series of worked examples, we show how formally representing a theory of mind as a memo-like programming language can lend insight into a variety of theoretical issues in theory-of-mind research: (1) how a single, fixed intuitive theory can be used to reason about social situations with unbounded structural variation; (2) how a modular, domain-specialized, and informationally-encapsulated system for social cognition might interface with external world knowledge, as well as other cognitive systems like intuitive physics; and (3) how different theories of mind, such as those of children and adults, differ, what exactly is gained as theories grow over the course of development, and how that growth might occur.</summary>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-17T02:26:27Z</published>
    <arxiv:primary_category term="cs.PL"/>
    <author>
      <name>Kartik Chandra</name>
    </author>
    <author>
      <name>Jonathan Ragan-Kelley</name>
    </author>
    <author>
      <name>Joshua B. Tenenbaum</name>
    </author>
    <author>
      <name>Rebecca Saxe</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.19545v1</id>
    <title>Where the LLM Ends and Reliable Decisions Begin</title>
    <updated>2026-09-17T01:13:09Z</updated>
    <link href="https://arxiv.org/abs/2609.19545v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.19545v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>Systems that turn natural-language descriptions of optimization problems into solver-ready code generally use a language model at every stage, including the final translation from a mathematical formulation into executable model-building code. We propose the ANVIL compiler architecture, where we separate these concerns. A language model is called only once, assisted by constraint guidance based on problem type, to produce a LaTeX formulation. A deterministic compiler then translates that LaTeX into code with no language model involvement. We describe the deterministic compiler (a normalizer, a recursive-descent parser producing a typed intermediate representation, analysis passes that bind symbols to a dataset schema, and a code emitter) and evaluate it on the 354 easy and hard problems of the NLP4LP benchmark. The compiler produced code for 329 of 354 formulations (92.9%), taking the deterministic path in every one of those cases and never falling back to model-generated code. Median compile time was below the 10ms resolution of our timer. Overall, our formulations achieved an accuracy of 98.9% over easy problems and 91.1% for hard problems. The gap between these compilation and accuracy figures is a key point of analysis, and we analyze it: formulations that failed to compile, problems that returned as infeasible, problems raising errors at runtime, and problems returning a wrong objective. Almost all of these errors trace back to the formulation rather than to the translation. ANVIL performs exceptionally well on leading benchmarks by using language models purely where they are effective, rather than as a catch-all tool.</summary>
    <category term="math.OC" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-17T01:13:09Z</published>
    <arxiv:primary_category term="math.OC"/>
    <author>
      <name>Priyadarshan Patil</name>
    </author>
    <author>
      <name>Abhishek Basu</name>
    </author>
    <author>
      <name>Vikas Reddy</name>
    </author>
    <author>
      <name>Abhinav Gupta</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.19531v1</id>
    <title>Detecting Soft Errors in Parallel Software with LLM-tuned Instruction Duplication</title>
    <updated>2026-09-17T00:54:35Z</updated>
    <link href="https://arxiv.org/abs/2609.19531v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.19531v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>We propose PaRID (PaRallel Instruction Duplication), a software-directed soft error detection framework that requires only compile-time effort for multithreading parallel programs. PaRID addresses two key challenges: supporting parallel programs with mixed serial and parallel regions and minimizing performance overhead without relying on costly dynamic profiling. It combines parallel-aware code transformation with LLM-tuned performance modeling, guided by eight generalizable findings from an offline characterization study, to enable fast soft error detection in parallel applications. Evaluation on NPB benchmarks shows that PaRID reduces protection overhead from 162.79% to 59.84% on average and achieves up to 5x speedup while maintaining full error detection effectiveness.</summary>
    <category term="cs.DC" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.AI" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-17T00:54:35Z</published>
    <arxiv:primary_category term="cs.DC"/>
    <author>
      <name>Yafan Huang</name>
    </author>
    <author>
      <name>Guanpeng Li</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.14527v2</id>
    <title>Equality saturation theory exploration à la carte</title>
    <updated>2026-09-18T14:36:26Z</updated>
    <link href="https://arxiv.org/abs/2609.14527v2" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.14527v2" rel="related" type="application/pdf" title="pdf"/>
    <summary>Rewrite rules are critical in equality saturation, an increasingly popular technique in optimizing compilers, synthesizers, and verifiers. Unfortunately, developing high-quality rulesets is difficult and error-prone. Recent work to automatically infer rewrite rules does not scale to large terms or grammars. Users struggle to guide inference and incrementally construct rulesets because existing rule inference tools are monolithic and opaque. As a result, most equality saturation users still manually develop and maintain rulesets.
  This paper proposes Enumo, a new domain-specific language for programmable theory exploration. Enumo provides a small set of core operators that enable users to strategically guide rule inference and incrementally build rulesets. Short Enumo programs easily replicate results from state-of-the-art tools like Ruler, but Enumo programs can also scale to infer deeper rules from larger grammars than prior approaches. Enumo's composable operators even facilitate developing new strategies for ruleset inference. We introduce a new fast-forwarding strategy which does not require evaluating terms in the target language, and thus supports domains that were out of scope for prior work. Enumo is also easy to extend: two new operators suffice to incorporate large language models into rule inference, where they complement guided search.
  We evaluate Enumo and fast-forwarding across a variety of domains. Compared to state-of-the-art techniques, Enumo can synthesize better rulesets over a diverse set of domains, in some cases matching the effects of manually developed rulesets in systems driven by equality saturation.</summary>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-13T14:06:39Z</published>
    <arxiv:comment>43 pages, 9 figures, Extended version of the OOPSLA 2023 paper, submitted to the Journal of Functional Programming. v2: corrected the accent in the title metadata; paper unchanged</arxiv:comment>
    <arxiv:primary_category term="cs.PL"/>
    <author>
      <name>Anjali Pal</name>
    </author>
    <author>
      <name>Brett Saiki</name>
    </author>
    <author>
      <name>Ryan Tjoa</name>
    </author>
    <author>
      <name>Cynthia Richey</name>
    </author>
    <author>
      <name>Amy Zhu</name>
    </author>
    <author>
      <name>Oliver Flatt</name>
    </author>
    <author>
      <name>Max Willsey</name>
    </author>
    <author>
      <name>Zachary Tatlock</name>
    </author>
    <author>
      <name>Chandrakana Nandi</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.06743v1</id>
    <title>Staged Hybrid Quantum-Classical Programming</title>
    <updated>2026-09-06T17:35:18Z</updated>
    <link href="https://arxiv.org/abs/2609.06743v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.06743v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>Hybrid quantum-classical computing systems consist of a classical control system that sends quantum circuits and receives measurement results from a quantum co-processor. Such systems allow us to model algorithms that require the classical control system to generate quantum circuits on the fly, potentially based on prior measurement results. This is challenging, as the classical control system must generate quantum circuits that manipulate live quantum states. In this setting, the classical control system is generating further quantum circuits while the quantum co-processor is internally maintaining the state of the live qubits; this is not ideal, since this not only is costly but also introduces additional sources of noise to the live qubits. Thus, we want to minimize the latency between receiving measurement results and sending the next quantum circuit to be executed by pre-computing quantum circuits.
  We introduce HyQ (pronounced haiku), a multi-modal language based on adjoint logic that pre-generates quantum circuits before executing a hybrid quantum-classical program. We achieve this by separating our semantics into two distinct stages: 1) compile-time generation of quantum circuits and classical runtime code and 2) execution of the classical runtime code that instruments the quantum co-processor. This separation between stages allows us to formally guarantee that all circuit-generation logic occurs before the instrumentation logic, i.e., the actual runtime, and minimizes the idling of the quantum co-processor at runtime. We give a type system, a circuit-normalization semantics for the compile-time stage, which eagerly performs all circuit-generation logic, and a runtime semantics for HyQ that corresponds to the second stage. We prove type preservation and progress for both semantics.</summary>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.LO" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-06T17:35:18Z</published>
    <arxiv:primary_category term="cs.PL"/>
    <author>
      <name>Chuta Sano</name>
    </author>
    <author>
      <name>Peng Fu</name>
    </author>
    <author>
      <name>Ryan Kavanagh</name>
    </author>
    <author>
      <name>Jennifer Paykin</name>
    </author>
    <author>
      <name>Brigitte Pientka</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2609.04585v1</id>
    <title>JLIR: A Julia-Native MLIR-Inspired Intermediate Representation with Automatic JACC Kernel Extraction</title>
    <updated>2026-09-04T00:35:54Z</updated>
    <link href="https://arxiv.org/abs/2609.04585v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2609.04585v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>The Multi-Level Intermediate Representation (MLIR) has made reusable compiler infrastructure practical for domain-specific computation. However, MLIR's strong compile-time type requirements and low-level (C++) extension model can be a poor match for high-level, dynamically specialized languages such as Julia. MLIR has several drawbacks for dynamic programming languages in terms of the type system and level of abstraction. It is thus extremely challenging for non-compiler or scientific computing users to introduce new programming abstractions and express algorithm implementations in a form that remains both natural and optimizable. As a result, library interfaces for linear algebra, mesh processing, partial differential equations, and related domains often sit outside the compiler optimization path. We present JLIR (Julia-native Level Intermediate Representation), a Julia-native intermediate representation framework that brings the main benefits of MLIR-style multi-level, dialect-oriented compilation into the Julia ecosystem while remaining usable as ordinary Julia code. JLIR represents Julia programs before low-level lowering, supports extensible operations and transformation passes through Julia's language mechanisms, and allows partially typed programs to remain transformable until concrete types are known. The framework includes built-in dialects for arithmetic, control flow, functions, structured loops, and memory operations, and it also includes a lightweight mechanism for adding new domain operations without modifying the core system. To demonstrate JLIR's capabilities, we applied it to automatic Julia for Accelerators (JACC) kernel generation.</summary>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.CL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-09-04T00:35:54Z</published>
    <arxiv:primary_category term="cs.PL"/>
    <author>
      <name>Narasinga Rao Miniskar</name>
    </author>
    <author>
      <name>Seyong Lee</name>
    </author>
    <author>
      <name>Keita Teranishi</name>
    </author>
    <author>
      <name>Jeffrey S Vetter</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2608.22624v1</id>
    <title>Rust for Secure Backend Development: A Critical Review and Extended Vulnerability Comparison with Node.js and Django</title>
    <updated>2026-08-23T22:15:10Z</updated>
    <link href="https://arxiv.org/abs/2608.22624v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2608.22624v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>The Rust programming language is widely credited with eliminating entire classes of memory-safety and concurrency vulnerabilities, but the security implications of adopting it in practice extend well beyond memory safety. This paper presents a critical review of prior work on Rust's security posture in industrial settings, and extends that analysis in a direction the original study did not cover: backend web development. We first assess the strengths and limitations of the existing vulnerability classification of Rust against C, C++, and Java under the SANS Top 25, OWASP Top 10, and the 19 Deadly Sins of Software Security frameworks, identifying gaps including limited empirical validation, a small interview sample, and the absence of a secure development lifecycle discussion. We then contribute an original comparison of Rust against Node.js and Django using the same three-level classification (Rare and Difficult, Safeguarded, Unprotected), supported by side-by-side code experiments for out-of-bounds writes (CWE-787), use-after-free (CWE-416), and race conditions (CWE-362). Our results indicate that Rust's compile-time guarantees dominate at the systems layer, while managed backend frameworks offer stronger built-in defenses at the application layer, suggesting that Rust adoption in web contexts requires complementary safeguards rather than reliance on language-level safety alone.</summary>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.CR" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-08-23T22:15:10Z</published>
    <arxiv:comment>10 pages, 5 tables. Critically reviews and extends Gasiba and Amburi, "I Think This is the Beginning of a Beautiful Friendship: On the Rust Programming Language and Secure Software Development in the Industry," CYBER 2023, pp. 19-26</arxiv:comment>
    <arxiv:primary_category term="cs.PL"/>
    <author>
      <name>Md Zarzees Uddin Shah Chowdhury</name>
    </author>
    <author>
      <name>Rabib Jahin Ibn Momin</name>
    </author>
    <author>
      <name>Rifat Shahriyar</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2608.20137v1</id>
    <title>Formal Performance and Compile Time Guarantees for Compiler Optimization Heuristics</title>
    <updated>2026-08-20T15:02:11Z</updated>
    <link href="https://arxiv.org/abs/2608.20137v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2608.20137v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>Modern optimizing compilers rely on heuristic search algorithms for NP-hard optimization problems, which can result in poor generated-code performance and long or unpredictable compile times. These are considered bugs by users, but verified compilers rarely reason beyond semantic preservation. We propose verifying performance and compile time properties of compiler passes. As a proof-of-concept, we formulate inline expansion using a cost model estimating instruction-cache performance. We mechanize this in Rocq, prove semantic preservation of the inlining transformation, and verify the algorithm's monotone improvement, convergence-time bound, and performance bounds for intermediate and final solutions.</summary>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.PF" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-08-20T15:02:11Z</published>
    <arxiv:comment>To appear in Formal Methods in Computer-Aided Design 2026 (FMCAD '26) Student Forum. 3 pages</arxiv:comment>
    <arxiv:primary_category term="cs.PL"/>
    <author>
      <name>Nikil V. Shyamsunder</name>
    </author>
  </entry>
  <entry>
    <id>http://arxiv.org/abs/2608.19889v1</id>
    <title>Write Once, Run Everywhere: The Axon DSL for Shape-Safe and Framework-Agnostic LLM Architectures</title>
    <updated>2026-08-20T10:56:34Z</updated>
    <link href="https://arxiv.org/abs/2608.19889v1" rel="alternate" type="text/html"/>
    <link href="https://arxiv.org/pdf/2608.19889v1" rel="related" type="application/pdf" title="pdf"/>
    <summary>The entire ecosystem of open-source language models effectively relies on a single platform. What if this platform was forced to shut down tomorrow? Implementing and maintaining efficient model definitions and translating them between different training and inference regimes is a resource-heavy task that severely limits model efficiency and portability, hindering both scaling and deployment. Here, we present Axon, a strongly typed domain-specific language with Haskell-like syntax, that enables a write-once, run everywhere paradigm for LLM architectures. By basing collaboration on a language specification rather than a specific framework's vision, Axon fosters open cooperation and empowers researchers to implement highly specialized architectures without giving up optimization infrastructure or accepting deployment lock-in. Axon allows for concise, auditable specifications that can be automatically compiled to standalone implementations for leading frameworks: PyTorch, PyTorch with Triton, JAX, MLX and vLLM. In 467 inference benchmarking experiments on models ranging from 135M to 32B parameters, we demonstrate median speedups of 7% on PyTorch, 12% on PyTorch with Triton, 91% on JAX, and 107% on MLX, compared to the reference implementations from Transformers. When deployed as native vLLM architectures with PagedAttention and KV-cache, Axon models achieve a 58% median speedup over Transformers implementations.</summary>
    <category term="cs.AI" scheme="http://arxiv.org/schemas/atom"/>
    <category term="cs.PL" scheme="http://arxiv.org/schemas/atom"/>
    <published>2026-08-20T10:56:34Z</published>
    <arxiv:primary_category term="cs.AI"/>
    <author>
      <name>Jacob Nielsen</name>
    </author>
    <author>
      <name>Danial Namazifard</name>
    </author>
    <author>
      <name>Lukas Galke Poech</name>
    </author>
    <author>
      <name>Peter Schneider-Kamp</name>
    </author>
  </entry>
</feed>
