Re:Microsoft Supercharges Bing Search With Programmable Chips
by gabbo on Monday June 16, 2014 @05:49PM
(#7901677)
FPGAs are something you tell what to be, not what
to do (and high level languages tell CPUs what to
do, not what to be).
That's a really great way of putting it. I never thought of it that way before, but you're spot on.
Re:Microsoft Supercharges Bing Search With Programmable Chips
by joshu on Monday June 16, 2014 @03:33PM
(#7900995)
Yeah, this rant makes me wonder if poster actually understands how these things work in deep detail.
Re:Microsoft Supercharges Bing Search With Programmable Chips
by zackmorris on Monday June 16, 2014 @07:44PM
(#7902112)
I used VHDL for a semester back in 98 or 99 for my ECE degree. I remember it being extraordinarily brittle compared to something like C, because there were so many ways to trigger unreliability with the wrong clock edges etc. So for example we did almost everything as state machines instead of math. The code was basically unmaintainable by today's standards but was an important learning tool. As I recall, we wrote a VGA signal generator, and if you had less than half a dozen incorrect pixels onscreen, you were doing pretty well. So in fairness, I USED to know this stuff in nauseating detail.
Re:Microsoft Supercharges Bing Search With Programmable Chips
by joshu on Monday June 16, 2014 @08:58PM
(#7902331)
Yes, this is because VHDL is not code. It's a different paradigm entirely. The FPGA doesn't "run" the VHDL, etc.
The units in an FPGA are just a little bit of logic with a bunch of connectivity to local busses.
I haven't done much VHDL lately (ECE '96 here) but I do remember how the stuff works. But then again I focused mainly on CPU architecture.
I fail to see how not having proprietary middleware will enable you to program an FPGA in Go or MATLAB.
FPGA's are not well suited to being programmed in conventional languages (and go is not a parallel language, it employs a clever model that may give you that impression but under the hood it is fairly regular, nothing you could not achieve using co-routines and threads in a different language, maybe syntactically cleaner and easier to understand). MATLAB might be more feasible but still not an easy match. You could conceivably make an FPGA co-processor though that you access from those languages through some library.
If you want to program an FPGA in something that looks like a high level language syntactically there are a number of solutions:
http://stackoverflow.com/questions/5603285/c-to-hardware-com...
And some newer developments. But none of those change the essence of the chip.
I'm not sure how to convey the difference between an FPGA and something like a high level language any better than 'imagine all your code executing at once'.
FPGAs are something you tell what to be, not what to do (and high level languages tell CPUs what to do, not what to be).