One Engine, Every EDA Format (Serge Rabyking) @FOSSiFoundation
One Engine, Every EDA Format (Serge Rabyking)  @FOSSiFoundation
Uploaded September 2026 | Updated November 2026, 2 days ago
Every EDA tool reimplements its own LEF/DEF/GDSII/Tcl readers. rawast replaces them with one universal engine where the grammar is data — a runtime .rawast file, not compiled code. One engine parses any text or binary format into a queryable value tree, and because it’s bidirectional, the same grammar re-emits the text too. It’s self-hosting, GDSII is the worked binary example, and a planned container lets downstream tools parse once and never re-parse. The PoC parses a 3,132-file production corpus across four formats. C++17 + Python, MIT.
One Engine, Every EDA Format (Serge Rabyking)RVVTS: Open-Source RTL Bug Hunting for Complex RISC-V ISA Extensions (Manfred Schlägl)From DigitalJS to Coreblocks: Building Open Hardware Tools for Education (Marek Materzok)APyTypes: Configurable data types in Python for finite word-length simulations (Theodor Lindberg)Beyond the Open PDK:Progress in DI-OCDCpro, SG13CMOS5L and Open Design Challenges (Christian Wittke)Surfer - another year of new features (Oscar Gustafsson)Standing On the Shoulders of Tiny Giants (Razine Moundir Ghorab)Open-Source Logic Synthesis: ABC, mockturtle, and Beyond (Yukio Miyasaka)
FOSSi Foundation |

One Engine, Every EDA Format (Serge Rabyking)

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER