News for hackers. Stuff that matters.
Re:Intel Licenses ARM Technology to Boost Foundry Business by djcapelis on Tuesday August 16, 2016 @05:11PM (#12300686)
Intel's always maintained some of the leading fabs with technology usually a fair bit ahead of their competitors, but it is losing an entire segment of the processor design space. It is pretty big news that instead of continuing to make their own plays at these markets, (which haven't worked out) they're allowing others to ship their own ARM designs using their fabs. Intel's competitive advantage has always had a lot to do with the integration and bundling of world class fabrication technology and their processor designs pushing each other forward.

They've increasingly broken this cycle in the past few years, with the final demise of tick-tock and the continued number of devices which opt for ARM.

It's another in a series of developments that are reshaping the processor market and slowly moving Intel from a dominant position to a supportive one.

There's still a large number of brilliant engineers and amazingly competent people there. I wonder when they're gonna start really fighting for their future.

Re:Intel Licenses ARM Technology to Boost Foundry Business by lnanek2 on Tuesday August 16, 2016 @07:07PM (#12301331)
"fighting for their future" is often shooting themselves in the foot in my experience. A company I was at agreed to transition off of ARM to x86 for the next cost down revision of their embedded product. During the negotiations Intel promised libhoudini ARM translation support. Once we were committed and many weeks down the design path with development boards they broke their promise and refused to provide libhoudini. It was a really terrible position to be in because Intel was forcing us to get all our very expensive third party software relicensed in x86 versions, and we had no money for that. Honestly, we would have been a lot better off just sticking with ARM instead of buying Intel's lies. In the end, if Intel had provided an ARM option, though, they would have been a competitive solution at least instead what they were which was just a bad idea. So this insistence on fighting to get companies on x86 is not helping them necessarily.
Re:Intel Licenses ARM Technology to Boost Foundry Business by djcapelis on Tuesday August 16, 2016 @07:19PM (#12301390)
I agree their existing attempts have been disheartening and hard to watch.

I don't think fighting for their future necessarily involves keeping x86 as their only chip architecture.

I think that right now their "fights" and entries into these markets have mostly involved trying to keep the world from changing, not really fighting to survive. Less new and interesting strategies, more taking out old dusty x86 cores, polishing them up a bit and shoving them into the packages and market segments where they aren't dominant.

This is their fault at this point. It used to be that without x86 compat, you had an uphill battle. They don't have that high ground anymore. The fact that companies like yours were more locked to ARM than other options should be a huge, amazingly large warning sign for them.

I think what they should have done was the work the RISC-V team already started. I'm not sure they have the right architects to do it there though, frankly. The last time they tried to start a new architecture they really messed up on keeping it simple and providing clean hardware. They didn't recover confidence after Itanium and I think there was probably a lot of "Never Again" sentiment (probably rightfully so) both inside and outside the company.

But I think at some point it is going to become clear to them that they don't have any option but to try a move that desperate and risky again if they want to be a dominant player in the processor design business in the future.

Who knows if they'll actually get it right though. I probably would bet against it and would expect them to shift more and more towards a legacy designer (see also IBM) with substantial fab tech and capabilities that remain world class even if the processor design part loses most of the device markets.

Re:Intel Licenses ARM Technology to Boost Foundry Business by mariuolo on Wednesday August 17, 2016 @03:59AM (#12303091)
> During the negotiations Intel promised libhoudini ARM translation support. Once we were committed and many weeks down the design path with development boards they broke their promise and refused to provide libhoudini.

How come this wasn't put in the contract?

Re:Intel Licenses ARM Technology to Boost Foundry Business by gameshot911 on Tuesday August 16, 2016 @07:43PM (#12301494)
What ended up happening? Did Intel breach any contract they had with you guys?
Re:Intel Licenses ARM Technology to Boost Foundry Business by MawNicker on Tuesday August 16, 2016 @07:41PM (#12301486)
I'm amazed at the features they've crammed into x86 without breaking compatibility; Definitely impressive. That being said haven't they perverted the whole industry with this tactic? It seems like we ought to have switched from CISC to RISC. From a purely technical perspective at least. Microcode just seems like a run-time mini compiler. If it were just part of the actual compiler wouldn't that save power and heat? Could it hurt performance in some circumstances? Does CISC have any technical merit at all? I would love for this to have been motivated by something other than their x86 patents.
Re:Intel Licenses ARM Technology to Boost Foundry Business by dbcurtis on Tuesday August 16, 2016 @10:18PM (#12302070)
> It seems like we ought to have switched from CISC to RISC.

If you ever have a question about computer architecture, ask two questions: 1) where does the memory bandwidth go, and 2) where does the die area go. All else follows from this.

RISC only made sense when CPU clock speeds were at rough parity with central memory speed, on-chip I-caches were limited, pipelines were short, and compilers were only good at modest optimizations.

If you look at functionality per instruction byte, RISC is fairly low. In today's world, CPU clocks are hugely faster than memory speeds, on-chip I-Caches are huge, pipelines are very very deep, branch prediction hardware is very good, and compiler back-ends are much much smarter than the peak days of RISC. CISC wins because the amount of functionality that you can move into the I-Cache per clock is higher and the amount of functionality you can keep in a given amount of I-Cache die area is higher, and compilers are good enough to target specialized instructions efficiently.

Is what Intel has crammed into X86 impressive? Yes, very. And it was damn hard work. I can tell you that walking all the way out to byte 15 of an instruction to look at the MOD R/M byte to decide if you have to raise an illegal instruction exception is a painful long path to squeeze under the clock constraint. But breaking backwards compatibility is just not something customers will put up with. So logic and circuit designers get to ply their trade in it's most convoluted form with the X86.

Perhaps these days I should amend my question list and add a third: 3) where does the power go? This is where ARM has an advantage over X86. The equations that you have to resolve to issue an X86 instruction are simply more complex than for ARM, and all that bit-flipping consumes power.

Re:Intel Licenses ARM Technology to Boost Foundry Business by legulere on Wednesday August 17, 2016 @06:38AM (#12303599)
> If you look at functionality per instruction byte, RISC is fairly low.

You should watch this video: https://www.youtube.com/watch?v=Ii_pEXKKYUg

The most important information therein is that the difference in code density is minuscule between x86, ARM and RISC-V. The differences between GCC versions is even bigger.

> The equations that you have to resolve to issue an X86 instruction are simply more complex than for ARM, and all that bit-flipping consumes power.

It's actually just 3-10% of power consumption [1] and I even heard it claimed that the instruction decoding on ARM is larger than x86

[1] https://www.usenix.org/system/files/conference/cooldc16/cool...

Re:Intel Licenses ARM Technology to Boost Foundry Business by microcolonel on Wednesday August 17, 2016 @09:49AM (#12304634)
Adding to your point; I don't think we can even consider ARM to be a RISC, as Chris Celio is quick to point out in that presentation. It has instructions which are very nearly as complex as x86s, and each year they come closer to having as many as x86 has as well.
Re:Intel Licenses ARM Technology to Boost Foundry Business by renox on Thursday August 18, 2016 @09:14AM (#12312208)
> I don't think we can even consider ARM to be a RISC,

ARMv7 OK, is-it still true with ARMv8? It seems to be a much more 'reduced' ISA.

Re:Intel Licenses ARM Technology to Boost Foundry Business by microcolonel on Thursday August 18, 2016 @10:04AM (#12312521)
Every ARMv8 is also an ARMv7; since ARMv8 includes AArch32 in addition to AArch64. It still has Jazelle traps. It also has an 8-byte (though they brag that they only have 4-byte opcodes now) AES round instruction, and a SHA-256 permutation instruction.

Admittedly some of AArch64 is much cleaner, it involves fewer new conditional instructions than you would expect for an ARM architecture; however it sure as hell ain't RISC.

Re:Intel Licenses ARM Technology to Boost Foundry Business by Altay- on Wednesday August 17, 2016 @03:42AM (#12303049)
>But breaking backwards compatibility is just not something customers will put up with.

There's no reason to believe this to be an immutable law going forward for much longer. With more and more going into the browser & cloud, how much is really left on the client side to be backwards compatable with these days?

The first thing I do when I reformat is install chrome, login, and sync my Google Account. I have all my important documents on Google Drive, a full office suite in Google Docs, all my bookmarks, account logins, etc.

Re:Intel Licenses ARM Technology to Boost Foundry Business by pjmlp on Wednesday August 17, 2016 @04:15AM (#12303142)
Many of us don't live in the browser.

Personally for me the web is HTML + CSS, for everything else there is a native application, even though I have done my share of web application projects.

I also don't put my private data in the hands of strangers.

Also do know lots of people that think like I do.

Re:Intel Licenses ARM Technology to Boost Foundry Business by krylon on Wednesday August 17, 2016 @07:24AM (#12303829)
> With more and more going into the browser & cloud, how much is really left on the client side to be backwards compatable with these days?

For desktops/laptops and mobile phones, this may be true. For embedded device (where a lot of ARM chips end up) it is not an option, usually.

Likewise, on Windows, there is a huge amount of third-party software that is, for better or worse, tied to the CPU architecture. And for a fair amount of that software, vendors are either unwilling to port it to a new CPU or have stopped supporting the software altogether (or have gone out of business). Consider the sad fate of Windows RT. Windows on low-end ARM devices might have been sweet (as far as Windows goes), but if the only piece of software it runs is IE/Edge and Office, it is not terribly useful.

Re:Intel Licenses ARM Technology to Boost Foundry Business by stevefolta on Thursday August 18, 2016 @12:06AM (#12310381)
> RISC only made sense when CPU clock speeds were at rough parity with central memory speed, on-chip I-caches were limited, pipelines were short, and compilers were only good at modest optimizations.

No, RISC was a response to CPUs becoming faster relative to memory access. Smaller decode logic meant more die space for registers and cache.

Re:Intel Licenses ARM Technology to Boost Foundry Business by gaius on Wednesday August 17, 2016 @03:31AM (#12303019)
If this were entirely true, VLIW would have been a clear win, but in practice it wasn't.

ARM conditional execution is very clever.

Re:Intel Licenses ARM Technology to Boost Foundry Business by Symmetry on Wednesday August 17, 2016 @09:06AM (#12304344)
They work great in some situations, like playing back an MP3. If you're working with some problem where the memory accesses are either local or predictable enough that the prefetcher can guess right than a VLIW should be able to extract just as much parallelism as an OoO core and with less power. It's when you start suffering regular cache misses and the careful choreography of your VLIW instruction stream is thrown off that they start to lose. Which is most GUI programs, classical AI, web browsers and basically most things people do on desktops and servers so it's no surprise they lost there. But there are still lots of places in embedded computing where they're ubiquitous for good reason and your phone might very well have one in it too to offload some tasks to.
Re:Intel Licenses ARM Technology to Boost Foundry Business by gpderetta on Wednesday August 17, 2016 @05:00AM (#12303265)
> ARM conditional execution is very clever.

also mostly dead in 64bit armv8

Re:Intel Licenses ARM Technology to Boost Foundry Business by Symmetry on Wednesday August 17, 2016 @09:09AM (#12304356)
They have a special instruction now to predicate the next N instructions or not. In out of order implementations you want each instruction to have as few inputs as possible and my understanding was that the implicit input in the form of the branch information was causing problems. I've heard conflicting things about whether ARM processors split predicated instructions into two ops during decode.
Re:Intel Licenses ARM Technology to Boost Foundry Business by gpderetta on Wednesday August 17, 2016 @09:36AM (#12304543)
I'm way out of my depth as I know next to nothing about the ARM ISA, but as far as I know, there is no special instruction to predicate the next N instructions; conditional jumps don't count of course [1]. ARM v8 does have a predicated select instruction, but some form of it are available on many modern instruction sets.

[1] interestingly, POWER8 is capable of converting unpredictable conditional jumps over a small number of instructions to conditional execution.

Re:Intel Licenses ARM Technology to Boost Foundry Business by legulere on Wednesday August 17, 2016 @06:43AM (#12303620)
VLIW is pretty much the same as a superscalar processor, except that the compiler has to do most of the work. Almost all high performance CPUs nowadays are superscalar.
Re:Intel Licenses ARM Technology to Boost Foundry Business by soulbadguy on Wednesday August 17, 2016 @11:07AM (#12305246)
Not quite, VLIW is basically a lock-step architecture. VLIW is much closer to a SIMD/GPU architecture then to a superscalar CPU
Re:Intel Licenses ARM Technology to Boost Foundry Business by djcapelis on Tuesday August 16, 2016 @08:02PM (#12301578)
I am not entirely disagreeing, but there are some interesting things one can do with a CISC processor.

Arguably code density can be higher on a CISC device. You'll note that ARM has implemented basically code compression in their ISA with thumb.

As for microcode on x86, most of the actual instructions running on the processor are pulled from L1 already translated. This used to be the trace cache, but after P4 that was dropped and now comes back as a u-op cache, meaning mostly that the instructions are stored in decoded format and so don't get run through translation again. (In P4's trace cache, branches were smashed and whole trace sequences up to three branches long were cached and then speculatively retrieved and executed.)

Interestingly, there's research that shows you can spend plenty of time and gates to optimize the instructions as they come out of translation and go into the trace or u-op cache without negatively affecting performance, which allows some optimization basically for free. No one would do this these days because it's extra power and heat, but it was seriously considered back in the gigahertz wars.

In addition, it should be noted that the translation between x86_64 and u-op is not super larger or challenging and is much much less challenging than most things we'd think about as a compiler pass.

Decoupling internal architecture from externally exposed ISA is not an unreasonable choice, but x86 is certainly no longer a highly desirable external interface these days either.

In a world where single thread performance isn't a significant differentiator, there's fewer reasons to use x86.

Re:Intel Licenses ARM Technology to Boost Foundry Business by mozumder on Tuesday August 16, 2016 @08:53PM (#12301766)
> It seems like we ought to have switched from CISC to RISC. From a purely technical perspective at least

Uh, no. CISC is far more efficient than RISC. You can do much more with fewer bytes, increasing your cache efficiency. Also, the fastest instructions are just as quickly decoded as RISC, if not faster. And any complex instructions we can leave for microcode.

The fact that early microprocessors are CISC shows you how much they could do with just a few thousand transistors. RISC architectures never took off until they could pack millions of transistors in, which should hint at how inefficient they were. This inefficiency manifests itself in modern times through power consumption. DEC Alphas & Power CPUS were already power consumption beasts, which is why Apple had to switch from Power to x86 for Macs.

Right now there is nothing intrinsically better about RISC architectures. Like VLIW, RISC is a nice theoretical computer-engineering experiment, nothing more.

Re:Intel Licenses ARM Technology to Boost Foundry Business by gvb on Tuesday August 16, 2016 @09:28PM (#12301898)
My take on the CISC/RISC "fight" is that the RISC was based on the assumption that the CPU clock was the limiting factor, so making a simpler CPU (RISC) would allow the CPU to be clocked faster than CISC and thus it would run faster.

This was the case briefly when RISC came out (e.g. Alpha), but x86 fought back with improved fab technology and also threw more power at the problem. Lots of power.

What blindsided RISC was that the CPU clock speed is not as much a limitation as memory access speed[1]. The voracious appetite of RISC instruction fetching[2] through the memory subsystem slowed it down more than it could speed up the CPU clock. (Yeah, yeah, broad generalizations.)

Oh man, my point in a great graphic! https://www.cs.virginia.edu/stream/

[1] If you run the numbers, todays DDRn SDRAM latency is maybe half the latency of the original IBM-AT even though the advertised when streaming bandwidth is several orders of magnitude faster. In other words, if you are not streaming the memory accesses, your memories are not much more than 2x faster than the IBM-AT. Caching enables streaming. Branches break the stream. That is why both caches and branch prediction logic is huge.

My numbers are out of date, but when I ran the numbers for the DDR2(?) memory in my hardware, the worst case latency was 56 clock cycles (e.g. if you had to close a page, open a new page, CAS latency, etc.).

[2] RISC takes 1.5-2x more instructions than CISC in my experience. YMMV.

Re:Intel Licenses ARM Technology to Boost Foundry Business by rayiner on Wednesday August 17, 2016 @12:08AM (#12302447)
CAS latency is about 13ns for DDR3/4. Back in the day 100ns RAM was typical.
Re:Intel Licenses ARM Technology to Boost Foundry Business by baobrien on Tuesday August 16, 2016 @09:36PM (#12301927)
This isn't always the case. Check out the RISC-V compressed extension. It turns out that RV64GC usually beats x86_64 on dynamic code size.

See slide 31: https://riscv.org/wp-content/uploads/2016/07/Tue1130celio-fu...

Re:Intel Licenses ARM Technology to Boost Foundry Business by freehunter on Tuesday August 16, 2016 @08:04PM (#12301587)
I can't answer the question of technical merit, but things hardly ever win public appeal based on technical merit. The appeal of x86 is the mountains of backward compatible software, which is due to how well-known its programming methods are, which is due to how incredibly popular the CPU type is. If we keep switching to the best possible CPU architecture every time a new one popped up, nothing would ever achieve what x86 has done.

English is far from the best language, but everyone on this site speaks it. Gasoline is far from the best source of fuel for a vehicle, but every corner has a gas station. x86 is far from the best architecture, but basically every OS at leasts supports it in some way.

Re:Intel Licenses ARM Technology to Boost Foundry Business by detaro on Tuesday August 16, 2016 @09:09PM (#12301819)
> If it were just part of the actual compiler wouldn't that save power and heat?

That gives less flexibility to the processor maker for individual optimizations. A CPU can optimize its microcode generation to use its hardware as efficiently as possible. Made a hardware change that can be used for more performance?

Update the microcode generator and ship the new CPU, all updated (complex) instructions build on that are automatically faster/more efficient/whatever you optimized.

If you compile to microcode-equivalent, your compilers don't know about the new detail, so they won't try to use it. So you need to ship a new CPU, and then update all compilers to know about your new microcode, and get software recompiled, and worst case shipped in both a version for your new and all old CPUs, ...

Giving the CPU abilities to change things about how it exactly executes code means the compiler has to know less about the specific CPU running the code later.

AFAIK this is one of the things that killed the Itanium line: they tried to rely on sufficiently smart compilers instead of hardware optimizations, and had a hard time to adapt the code running to innovations on the hardware level.

Re:Intel Licenses ARM Technology to Boost Foundry Business by icebraining on Wednesday August 17, 2016 @04:55AM (#12303245)
There's an alternative: running an optimization step after software installation, like Android's ART does.
Re:Intel Licenses ARM Technology to Boost Foundry Business by erichocean on Tuesday August 16, 2016 @08:00PM (#12301572)
> Does CISC have any technical merit at all?

Object code, in some cases, can be smaller. That's why modern RISC ISAs like RISC-V include a "compressed" instruction set option, to combat the object code size disparity with CISC ISAs.

Re:Intel Licenses ARM Technology to Boost Foundry Business by Unklejoe on Tuesday August 16, 2016 @08:08PM (#12301611)
I've heard of that. I believe it's used on some automotive computers (Bosch GS19 transmission controller comes to mind, which I think uses the Freescale MPC500).

I wonder how it works. If the opcodes can all be compressed, why not just make them smaller to begin with? I guess I always thought of opcodes as being enumerations of "commands".

Re:Intel Licenses ARM Technology to Boost Foundry Business by baobrien on Tuesday August 16, 2016 @09:33PM (#12301916)
In the case of RISC-V, the compressed extension only covers a subset of the full length instructions, but can be freely intermixed with them. It turns out that RV64GC (risc-v 64 bit with compressed instructions) usually beats x86_64 in dynamic instruction bytes.

See slide 31: https://riscv.org/wp-content/uploads/2016/07/Tue1130celio-fu...

Re:Intel Licenses ARM Technology to Boost Foundry Business by wolf550e on Tuesday August 16, 2016 @08:25PM (#12301670)
RISC instructions are all the same size in bits to achieve fast decode speeds. Thus you must choose between 32bit instructions or 16bit instructions. ARM supports both, including function calls from one to the other.
Re:Intel Licenses ARM Technology to Boost Foundry Business by plasticchris on Tuesday August 16, 2016 @08:43PM (#12301725)
This must have been solved, thumb 2 (https://en.wikipedia.org/wiki/ARM_architecture#Thumb-2) mixes 16 and 32 bit instructions.
Re:Intel Licenses ARM Technology to Boost Foundry Business by gvb on Tuesday August 16, 2016 @09:03PM (#12301806)
The 16 bit "thumb" instructions are still all fixed size - 16 bits. They do this by limiting the available options in the instructions. For instance, the register selection field will be 3 bits so only 8 registers can be directly accessed by the thumb instructions. They also drop some instructions IIRC.

The 16 bit instructions map 1:1 to the 32 bit instructions, so decoding is unchanged, The difference is a pre-decoding transmogrificaiton stage where some of the resulting fields in the transmogrified 32 bit instruction are fixed (e.g. 0) and some are filled in from the original 16 bit instruction fields.

Switching between 32 bit and "thumb" is fairly painless but the instructions cannot be intermingled. When you do a call, you have the opportunity to switch 32/thumb. When you return, the processor switches back as appropriate.

The resulting thumb code is more compact than full 32 bit instructions, but it isn't 2x more compact because you still need some 32 bit instructions (subroutines) and the 16 bit instructions are not as powerful as the full 32 bit instructions.

Re:Intel Licenses ARM Technology to Boost Foundry Business by oshepherd on Tuesday August 16, 2016 @10:08PM (#12302038)
Thumb-2 (about 13 years old at this point) extended Thumb to cover the entirety of instruction set. That is, every* ARM instruction has a corresponding Thumb instruction (The converse is not quite the case)

There is very little reason to use ARM code in ARMv7 and up.

Incidentally, ARMv8's 64-bit mode (AArch64) adds a whole new instruction set, called A64. It's fixed width 32-bit per instruction, and the only option for 64-bit code.

* Excluding some really obscure, mostly long deprecated ones

Re:Intel Licenses ARM Technology to Boost Foundry Business by oshepherd on Tuesday August 16, 2016 @10:23PM (#12302100)
I noticed that I missed out mentioning that, yes, Thumb-2 made Thumb variable length (it already sorta-was, branches were always kinda 32-bit)

Any halfword where bit[15:13]=='111' && bit[12:11]!='00' is the leading half of a 32-bit Thumb instruction

Re:Intel Licenses ARM Technology to Boost Foundry Business by baobrien on Tuesday August 16, 2016 @09:42PM (#12301946)
That's why I'm a fan of the RISC-V compressed ISA extension. Compressed instructions are 16 bits long and a subset of the 32 bit instructions, but can be mixed freely with 32 bit. The extension also relaxes the alignment requirements, so that 32 bit instructions can be aligned to 16 bit boundaries.
Re:Intel Licenses ARM Technology to Boost Foundry Business by Symmetry on Wednesday August 17, 2016 @09:20AM (#12304421)
Does CISC have any technical merit at all?

RISC and CISC are both philophies that rose out of the contstraints of the eras they originated in and both, in their pure forms, are totally obsolete.

The effort that goes into the design of a modern CPU micro architecture is so high that the number of instructions has a pretty small impact on the overall design effort. The descendants of the original RISC ISAs have kept adding new instructions and for good reason.

On the other hand part of the increase in micro architectural complexity is that chips are designed to decode and issue multiple instructions per clock cycle. So the ease of multiple decode where every instruction is aligned to 32 bit boundaries is actually a noticable advantage.

The size of the instruction stream is still an issue but on that front x86-64 and ARM-64 are more or less tied these days in terms of bytes of instruction per task so that's a wash in practice these days.

Re:Intel Licenses ARM Technology to Boost Foundry Business by rayiner on Tuesday August 16, 2016 @11:58PM (#12302424)
RISC versus CISC was a non-issue even 10 years ago. X86 was never that CISC-y, and x86-64 is straight up a pretty clean architecture, with a memory model that doesn't suck.
Re:Intel Licenses ARM Technology to Boost Foundry Business by pcwalton on Thursday August 18, 2016 @01:11PM (#12314364)
> x86-64 is straight up a pretty clean architecture, with a memory model that doesn't suck

I wouldn't go that far. In particular, the encoding of instructions in x86-64 makes zero sense except for backwards compatibility. Since all code is littered with REX prefixes, you have the same i-cache footprint as RISC architectures do without the benefits (die area for decoding, etc.).

If you fixed the instruction encoding, extended the three-address forms of instructions introduced in AVX2 to scalar integer operations, and finally threw away real mode and port mapped I/O, etc., I agree that x86-64 would be pretty nice. I'd be happy to get even one of those improvements, honestly :)

Re:Intel Licenses ARM Technology to Boost Foundry Business by legulere on Wednesday August 17, 2016 @06:59AM (#12303710)
The original x86 was pretty unriscy with the registers not being general purpose. The addressing modes to this day are still very CISCy
Re:Intel Licenses ARM Technology to Boost Foundry Business by fanf2 on Thursday August 18, 2016 @03:38AM (#12310938)
The addressing modes in x86 are much less CISCy than the VAX or 68040 - no multiple indirections or increments in one instruction. John Mashey explained well the difference http://yarchive.net/comp/risc_definition.html
Re:Intel Licenses ARM Technology to Boost Foundry Business by MawNicker on Wednesday August 17, 2016 @06:36AM (#12303591)
Too pithy for the down-voters apparently. This comment made me laugh. What x86 taught me is that: CISC = RISC + microcode.