Kodsnack 411 - The performance to generate the next CPU, with Wilson Snyder

44:44
 
Dela
 

Manage episode 288725265 series 2166142
Av Kristoffer, Fredrik, Tobias upptäckt av Player FM och Player FMs grupp - upphovsrättigheterna ägs av publiceraren, inte Player FM. Ljudet streamas direkt från deras servrar. Tryck på Prenumerera knappen för att hålla koll på uppdateringar i Player FM, eller klistra in flödets webbadress i andra podcast appar.

Fredrik chats with Wilson Snyder about Verilator, chip design, performance, and open hardware.

This episode is a bit of a follow-up to episode 389 where Robert Wikandertalked - in Swedish - about verification of circuit designs. Afterward, Robert mentioned that we should really ask Wilson Snyder to talk about Verilator, and here we are! Wilson works with CPU and other hardware design, and is one of the lead developers of Verilator. When you design hardware, hardware description languages come in handy - you use them to describe hardware precisely. Then you can generate runnable code simulating the hardware, and run batteries of tests against it without needing to manufacture physical hardware.

Verilator is one tool for turning code in the Verilog hardware description language into C++ or Systemc. The major competing tools are more on the interpreter side - which means that Verilator usually has a performance advantage. Oh, and it’s GPL licensed as well. As we discuss, Verilator doesn’t actually support all of Verilog, but that’s being worked on. And increased performance in itself is a clear goal of both research and concrete improvements.

We also discuss a bit what might come out hardware-wise in the future. Wilson predicts DPUs - data-offload units, basically - will become even more of a thing than today.

The second part of the discussion is focused on Verilator itself - how it’s built, designed, and developed. People with knowledge of compilers will feel right at home inside the Verilator source code.

Thank you Cloudnet for sponsoring our VPS!

Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlundand @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive.

If you enjoy Kodsnack we would love a review in iTunes! You can also support the podcast by buying us a coffee (or two!) through Ko-fi.

Links Titles
  • An open source tool that could do verification
  • It started as a hobby
  • It has a life of its own
  • Into actual hardware gates
  • Matching the languages
  • A good escape story
  • It’s bascially a compiler
  • Open source hardware design
  • The performance to generate the next CPU
  • Innovation feedback cycles
  • Download a core
  • Always a little bit of a focus
  • My real job is CPU design

428 episoder