VHDL's Crown Jewel
cokernel_hacker
12 points
1 comment
March 30, 2026
Related Discussions
Found 5 related stories in 79.8ms across 8,303 title embeddings via pgvector HNSW
- Show HN: FPGA soft-core of the Saab Viggen's 1963 airborne computer FormerLabFred · 18 pts · March 20, 2026 · 53% similar
- Building an FPGA 3dfx Voodoo with Modern RTL Tools fayalalebrun · 175 pts · March 22, 2026 · 50% similar
- Show HN: I built a RISC-V emulator that runs DOOM Flex247A · 37 pts · May 03, 2026 · 48% similar
- Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview GodelNumbering · 325 pts · April 27, 2026 · 46% similar
- SBCL: the ultimate assembly code breadboard (2014) yacin · 138 pts · May 20, 2026 · 46% similar
Discussion Highlights (1 comments)
e7h4nz
The Delta Cycle logic is actually quite similar to functional reactive programming. It separates how a value changes from when a process responds to that change. VHDL had this figured out as early as 1987. I spent many years writing Verilog test benches and chasing numerous race conditions; those types of bugs simply don't exist in VHDL. The Verilog rules—using non-blocking assignments for sequential logic and blocking assignments for combinational logic—fail as soon as the scenario becomes slightly complex. Verilog is suitable when you already have the circuit in your head and just need to write it down quickly. In contrast, VHDL forces you to think about concurrent processes in the correct way. While the former is faster to write, the latter is the correct approach. Even though SystemVerilog added some patches, the underlying execution model still has inherent race conditions.