https://www.altera.com/products/design-software/high-level-d...
These (almost by necessity) make you write code that doesn't look like any other C code. You can't just use some pre-existing C library and compile it to use FPGA resources. At that point, why not go a step further and just use a proper HDL?
You're assuming that you're starting with an FPGA only project. In reality most projects that are going to be accellerated with these Xeon+FPGA systems is existing software where only a handful of hotspots will have be ported to the limited C language which is significantly less effort than rewriting the entire algorithm in HDL.
It took me a while to grok HDL and write working code (good, maintainable code aside) even though I took digital design courses.
FPGAs don’t get firmware.
HDL is a description of hardware.
HDL can be referred to as code. And I do know what HDL is and what FPGAs are, thank you.
No, it can't. That's why the caps are there and I'm sticking to it. You basically justified it ;)
Code is something that you design to run sequentially. HDL is a description of gates and logic that runs all at the same time.
If you wanted to argue that the bitstream is firmware - that's a tougher discussion.
Unlike Xilinx, though, Intel (very very recently) just started offering their OpenCL-for-FPGA SDK for free, and it works on most of their device families, including Arria/Xeon and Cyclone/ARM. I always found it disappointing that the OpenCL SDKs were normally licensed, since they're more-or-less a logical extension of HLS support. So that's nice of Intel.
They don't have any equivalent to Xilinx SDSoC though, but for datacenter targets they're shipping a different set of SDKs anyway (called "OPAE"), so maybe in the future they'll build something on top of the OPAE and OpenCL support (e.g. single-source model, like Sycl)
Xilinx is already pushing it's Vivado HLx which is pretty much that. I'm not aware of Altera's current offerings but they won't overlook this so easily.