News for hackers. Stuff that matters.
Re:Why I will be using RISC-V in my next chip by e12e on Saturday January 09, 2016 @11:21PM (#10874133)
But aren't modern Intel and AMD CPUs internally RISC(-like)? It seems like we have great compilers for CISC targets, and can make great RISC CPUs that process CISC instruction sets really well?

Perhaps the issue is that the internals of eg. modern Intel CPUs are locked up at Intel, so the missing step from CISC assembly to efficient RISC is missing (while we've got high-level/C/C++ to CISC covered)?

Re:Why I will be using RISC-V in my next chip by Marat_Dukhan on Saturday January 09, 2016 @11:30PM (#10874168)
No they aren't internally RISC. On big Intel & AMD cores "ADD reg, mem" translates to a single uop. On Intel Atom even "ADD mem, reg" translates to a single uop. In fact, it is mostly legacy instructions (e.g. binary-coded decimal arithmetic) that are translated into multiple uops.
Re:Why I will be using RISC-V in my next chip by userbinator on Sunday January 10, 2016 @01:27AM (#10874464)
x86 uops are very wide, much wider than RISC instructions and more like VLIWs; P6 uops are 118 bits and I haven't easily found any description of the newer models but they are likely even wider.
Re:Why I will be using RISC-V in my next chip by Marat_Dukhan on Sunday January 10, 2016 @01:39AM (#10874485)
The latest number I have is 157 bits in Intel Core (for a ROB entry).