CPPL: A Circuit Prompt Programming Language

This is a good paper for undergraduates to dissect and find ways to make better.

"adversarially summarize this paper using an inverted-pyramid style" is a good starting point. I won't go into details beyond this, but the authors should be more critical of their own work.

The very first sentence: "Large language models (LLMs) have shown promise in register-transfer level (RTL) design automation" I want to see some serious proof for this shitty claim. While LLMs excel at slop webapp codegen because the code is usually highly modular, composable and easy to reason about), LLMs understanding of RTL is just pure dogshit. A simple signaling protocol, even well documented with some temporal behaviour and even some ready made assertions that are picked up by formal verification tools for static proving - none of this helps any top tier LLM to grok whats happening. state explosion, temporal dependencies, no composition - RTL is not code, its construction for complex machinery and LLM suck balls at it. and all of this will not go away if you slop into existence some low quality DSL for netlists

[flagged]