GenAI for Systems: Recurring Challenges and Design Principles from Software to Silicon
Organizations: Harvard University
Abstract
Generative AI is reshaping how computing systems are designed, optimized, and built, yet research remains fragmented across software, architecture, and chip design communities. This paper takes a cross-stack perspective, examining how generative models are being applied from code generation and distributed runtimes through hardware design space exploration to RTL synthesis, physical layout, and verification. Rather than reviewing each layer in isolation, we analyze how the same structural difficulties and effective responses recur across the stack. Our central finding is one of convergence. Despite the diversity of domains and tools, the field keeps encountering five recurring challenges (the feedback loop crisis, the tacit knowledge problem, trust and validation, co-design across boundaries, and the shift from determinism to dynamism) and keeps arriving at five design principles that independently emerge as effective responses (embracing hybrid approaches, designing for continuous feedback, separating concerns by role, matching methods to problem structure, and building on decades of systems knowledge). We organize these into a challenge--principle map that serves as a diagnostic and design aid, showing which principles have proven effective for which challenges across layers. Through concrete cross-stack examples, we show how systems navigate this map as they mature, and argue that the field needs shared engineering methodology, including common vocabularies, cross-layer benchmarks, and systematic design practices, so that progress compounds across communities rather than being rediscovered in each one. Our analysis covers more than 275 papers spanning eleven application areas across three layers of the computing stack, and distills open research questions that become visible only from a cross-layer vantage point.
Figures & tables
| Subsection | Challenges | Key principles | Description |
| 3.1 Software engineering | C1, C2, C3 | P1, P2, P3 | Generative and agentic systems that produce code edits, patches, and refactorings in large repositories, evaluated through build systems, test suites, and CI pipelines where implicit project conventions and non-local correctness constraints dominate outcomes. |
| 3.2 Performance engineering & code optimization | C1, C2, C4 | P2, P4, P5 | Learning-driven techniques for optimizing code, compiler flags, and program transformations using profiling feedback, where performance gains depend on hardware-specific behavior and tight coupling between compilers, runtimes, and microarchitectures. |
| 3.3 GPU kernels | C1, C3, C4 | P2, P4 | Automated synthesis and tuning of GPU kernels (e.g., CUDA, Triton), where correctness and performance are validated via expensive compile-run loops and are highly sensitive to memory access patterns, numerical behavior, and runtime interfaces. |
| 3.4 Distributed systems | C3, C4, C5 | P1, P2, P3 | Generative approaches to producing system configurations and policies for scheduling, networking, and collective communication, where changes affect live deployments and must remain safe under topology constraints and dynamically varying workloads. |
| 4.1 Performance prediction & DSE | C1, C2, C4 | P1, P2, P4 | Surrogate modeling and generative search methods for architectural design-space exploration, where expensive simulation or measurement limits feedback and proxy metrics encode tacit assumptions about performance and efficiency. |
| 4.2 Hardware accelerators & AI mappings | C2, C4, C5 | P2, P4, P5 | AI-assisted accelerator design and mapping techniques that determine dataflows, scheduling, and memory placement for ML workloads, tightly integrating model structure with compiler stacks and adapting to rapidly evolving architectures and models. |
| Required Capability | Methods | Benchmarks | Tools & Infra. | Deployment Evidence | Cross-Domain Transfer |
|---|---|---|---|---|---|
| 1. Fast, structured feedback loop Feedback Loop Crisis [C1] Continuous Feedback [P2] | ⚫ | ◗ | ◗ | ◗ | ❍ |
| 2. Independent validation infrastructure Trust & Validation [C3] Hybrid Approaches [P1] | ◗ | ◗ | ◗ | ◗ | ❍ |
| 3. Adaptive policies with safety guarantees Determinism to Dynamism [C5] Hybrid Approaches [P1] | ◗ | ❍ | ❍ | ◗ | ❍ |
| 4. Generator-verifier separation Trust & Validation [C3] Separate Concerns by Role [P3] | ◗ | ❍ | ❍ | ❍ | ❍ |
| 5. Captured and updatable domain knowledge Tacit Knowledge [C2] Build on Systems Knowledge [P5] | ◗ | ❍ | ❍ | ❍ | ❍ |
| 6. Cross-layer optimization interfaces Co-Design Across Boundaries [C4] Match Problem Structure [P4] | ◗ | ❍ | ❍ | ❍ | ❍ |
Electronic Design Automation
Electronic Design Automation uses algorithms and software to design, verify, optimize, and manufacture electronic circuits and systems.
See all 213 papers