6 ms·
I would ten to agree with Knuth's suggestion that multicore stuff and the "hardware jungle" is a symptom of a lack of imagination on the part of hardware design
by wglb 15y ago
I would ten to agree with Knuth's suggestion that multicore stuff and the "hardware jungle" is a symptom of a lack of imagination on the part of hardware designers.
- rbanffy 15y agoAs a hardware engineer myself, I must agree. We have only explored a tiny subset of all possible configurations with our computer designs, held back, perhaps, by the need to be binary-compatible with a hardware/software architecture that was obsolete in the mid 80's. It's time to do better.
- sounds 15y agoArm seems to do better than Intel. Perhaps an FPGA (using the term more broadly to include any field-reprogrammable logic array) can become more competitive performance/watt?
- jgw 15y agoThat can't really happen. FPGAs are just programmable ASICs. (Also, I'm not sure if you're suggesting that ARM cores are by their nature field-programmable. They're not, they're just IP cores that can be integrated into larger designs).
- Kliment 15y agoI think sounds is saying that a runtime-reconfigurable processor could be the next step forward, adapting itself to whatever task it has to do. I don't see much promise for speed improvements from this, but it is a cool idea.
- rbanffy 15y agoI am not talking about x86 vs. ARM. I am talking about computers that don't have CPUs connected through a bus to a single memory space. Someone else in this discussion mentioned the idea of fusing memristor memory with processing engines within the memory itself. That's the embryo of a very interesting idea - imagine hardware assisted memory deduplication, just to start.
- jgw 15y agoASIC guy here, too. The thing I find most alarming about hardware design is that functional simulation is reaching the end of its useful life because the majority of simulators are single-threaded. We're trying to keep up with Moore, and yet our simulation capacity has been plateaued for a few years now. And yet I hear very few ASIC designers and verification engineers complaining about it. We have formal tools, and FPGA prototyping, but by and large, most designs are verified and debugged under one of the big 3 simulators. I think a lot of software guys would be astounded at how backwards the ASIC design community is. To say nothing of the monstrosity that it SystemVerilog.
- eric-hu 15y agoOut of curiosity, how complex are these simulator tools? What sorts of physics and electrical engineering knowledge (in addition to CS knowledge for taking advantage of modern programming techniques) would one require to be able to write a minimum competing product?
- mynegation 15y agoComplicated enough to support companies with market cap of $3 Bn ($CDNS) and 1.5 Bn ($MENT) and these are just two leaders.
- jodrellblank 15y agoThat doesn't answer the question of a minimum competing product, they could be huge bureacratic cash cows...?
- deleted 15y ago[deleted]
- deleted 15y ago[deleted]
- jgw 15y agoTrue enough, but as I mentioned in my long ramble, what I'm talking about here are simulators, which make up just a small part of a design suite. (And Synopsys is larger than either Cadence or Mentor, actually)
- sliverstorm 15y agoI'm skeptical that different configurations could provide exponential improvements down the road. Architecture will always be limited by the speed of the clock, and in lieu of flops, the speed of the gates. (I am also skeptical that latches and/or stateless design will replace flops any time soon)
- LearnYouALisp 15y agoOnly five or six years ago a good chip had two cores and a clock rate of perhaps 2.4 gigahertz. Somehow the chips have been redesigned or improved to allow much lower heat loss at clock rates previously considered unreachable without special hardware. (A somewhat recent Intel chip is able to reach 4.4 gigahertz on four cores with air cooling, and AMD has eight-core server chips that produce less heat than older two-core chips.) I do not know how it was done, but apparently the engineers have found ways to improve their designs. Now the chips seem to be more powerful per clock cycle while producing less heat and reaching higher clock rates.
- wmf 15y agoOTOH, it seems arrogant to look at a $100B industry that has delivered astonishing things for decades and say "y'all need to try harder".
- srl 15y agoOTGH, the software industry is $300B (in the U.S. src: wp), and has had its own important part in delivering those astonishing things. If anyone's in place to say "y'all need to try harder" - it's us.
- sliverstorm 15y agoI don't follow. You are saying because the software industry has a larger cap it has been trying harder? Or something?
- LearnYouALisp 15y agoI thought the comment was going to be, the software industry has a worth of 300 billion dollars and look and the astonishing state of software, or, it needs to try harder...
- dkarl 15y agoI'm sure the imagination is there, but why bother creating hardware if programmers won't write code for it? Multicore and multinode systems are by far the least imaginative way around Moore's law, and they're the only thing 99% of software engineers are willing to touch. Not only that, programmers are fighting tooth and nail to keep using the same old languages no matter what the hardware architecture, because we are still sick with nostalgia for our single-core utopia. Compiling C to run on FPGAs is a thing that is actually done in the real world, for commercial purposes, which just makes me sick. In an ideal world, it would go like this. First, hardware engineers would come up with an idea for a programmable hardware architecture. Second, if the hardware worked well, language designers would figure out a language that was appropriate for the architecture. Third, if the language design step was successful, programmers would learn it and write programs for the new architecture. If you know ahead of time that the third step will always fail because learning strange new languages is assumed to be beyond the capability of 99% of programmers, then the second step (designing the language) is by definition impossible, which means the first step (designing a new programmable architecture) is also impossible. That's why hardware designers don't seem to have any imagination -- programmers have told them to stuff their imagination and concentrate on building machines that programmers already know how to program.