4 ms·
Looks like it's ultimately an llvm backend that'll generate VHDL, Verilog, or SystemC, and has some optimizations it'll do for the exact family of chip you're r
by monocasa 6y ago
Looks like it's ultimately an llvm backend that'll generate VHDL, Verilog, or SystemC, and has some optimizations it'll do for the exact family of chip you're running on. Knowing what the hard DSP blocks can do and writing code that'll use them kind of stuff (as well as a few farily generic optimization passes).
It doesn't appear to know anything about bitstreams and works at a higher level that'll be synthesized by another tool.
https://github.com/Xilinx/HLS/blob/da538325ea9cb410672be6bb15d6c2e6220bfeb3/llvm/llvm/lib/Target/FPGA/FPGA.td#L102 https://github.com/Xilinx/HLS/blob/da538325ea9cb410672be6bb1...
Awesome, fairly reusable looking work being opened by them. A lot more than I expected from the title. Good work, Xilinx!
- randrews9 6y agoThe article mentions its the HLS frontend that was open-sourced, not the backend. I see no evidence of any HDL codegen here at all yet. I'll keep looking though. The full HLS tool that they ship does produce full verilog/vhdl, and doesn't go to the bitstream level. It would be a huge improvement if they would open-source the whole thing. I suspect they will not, however, as code generator likely has a fairly complex FPGA Fabric/Slice timing model used to schedule operations into clocks, and that is something they would probably consider proprietary. Hopefully they can strip out those bits out and release the rest.
- AshamedCaptain 6y agoYeah, the final output is just LLVM IR, so this is about useless for anything. I'm not even sure this is the correct abstraction layer for an HLS tool (even though it seems 2 out of the 3 mayor players use it, albeit it is precisely the leader who doesnt use LLVM).