Re:Why hardware development is hard, part 1: Verilog is weir...
by vvanders on Thursday November 03, 2016 @12:52PM
(#12865666)
> If you need the user to describe gates and flip-flops and how they connect then make them describe this.
You're talking about RTL, which is exactly what these languages output.
Fundamentally they're not programming languages, unfortunately the initial instinct is to treat them as such and it leads to a ton of confusion.
Re:Why hardware development is hard, part 1: Verilog is weir...
by raverbashing on Thursday November 03, 2016 @02:27PM
(#12866575)
> You're talking about RTL, which is exactly what these languages output.
So why am I wasting time with verilog then if I have to "design" in low-level then translate it to verilog?
Re:Why hardware development is hard, part 1: Verilog is weir...
by wolfgke on Thursday November 03, 2016 @12:54PM
(#12865696)
> You're talking about RTL, which is exactly what these languages output.
If VHDL/Verilog would output RTL, you could easily analyze it just as you analyze assembly output of your favorite compiler. Unluckily the output is some proprietary bitstream for the FPGA.
Re:Why hardware development is hard, part 1: Verilog is weir...
by k0ngo on Thursday November 03, 2016 @01:09PM
(#12865839)
Just as a software compilation flow is devided into preprocessing, compilation, assembly, and linking, a HDL flow is divided into synthesis, mapping, place and route, timing analysis and bitstream generation. RTL is the output of the synthesis stage and is readily available to the designer, typically both as code and as a graphical schematic.
Maybe in really old compilers
> You don't write programs with it, you describe hardware with it
Which is fair enough, but it seems the "hardware description" pretends to be of a higher-level than it really is.
If you need the user to describe gates and flip-flops and how they connect then make them describe this.