<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VerilogCoder: Autonomous Verilog Coding Agents with Graph-based Planning and Abstract Syntax Tree (AST)-based Waveform Tracing Tool · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2408.08927/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2408.08927/feed.xml" rel="self" type="application/rss+xml" /><item><title>VerilogCoder: Autonomous Verilog Coding Agents with Graph-based Planning and Abstract Syntax Tree (AST)-based Waveform Tracing Tool — mentioned by Rochus</title><link>https://news.ycombinator.com/item?id=47029242</link><guid isPermaLink="false">urn:hackerpapers:mention:2408.08927:47029242</guid><pubDate>Mon, 16 Feb 2026 00:11:28 GMT</pubDate><description>&lt;p&gt;Cool. There has also been some effort for coding agents generating hardware descriptions e.g. in Verilog (see e.g. https://arxiv.org/html/2408.08927v1). Wonder how good they are today. Also in hardware design we could now switch to intent- and constraint based specifications in semi-formal human specification language and let the LLM write the SystemVerilog with assertions and do the testing.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2408.08927/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.AI</category></item></channel></rss>
