‹ BackHN Continuity

Thread

GPT-Synopsys: Frontier Intelligence to Revolutionize Chip Design

189 points · 111 comments · giuliomagnifico

  1. ducktective · · focus · HN ↗
    A question to those active in chip design industry: Are formal methods and formally proving a design more prevalent and normal in this industry compared to general software development?

    Like for a Arm microcontroller design, do engineers thoroughly test and formally prove the correct functionality of every component? If that's the case, why silicon errata is a thing?

    1. da-alex · · focus · HN ↗
      There are tools for formal verification of design input, and they are being used, but not for everything.

      Why there are still errata for silicon

      1. Writing a formal specification of your intended behavior is hard and the best verification tool doesn't help when your assertions don't encode the required or intended behavior. So even with 100% formal coverage, you would still get erratas. And some people don't write any formal verification, instead working with a simulation based approach (either hand-written test cases or random stimulus simulation) 2. Computation complexity of formal verification is exponential. At some point you simply can't formally prove the behavior of a design, because it just won't run on your server. 3. There's different levels of formal verification, not all of them are in the spec -> behavior path. For example, you could classify automated checks like logic equivalence between the synthesis netlist and RTL code as a formal verification. But that checks if the optimizer in the synthesis tool was correct, not that you wrote the correct RTL.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.