Watching the word widths expand is amusing in a way. The instruction words are beginning to look a lot like the old "microprocessors" with 96+ bit instructions. (If you can find a copy, a truly beautiful little book by White called "Bit Slice Design" is a great read. I taught from it for years.) Then there was the IBM Thorpe architecture: 128 bits, I think, and the machine had no program counter. So how do you think it handled subroutine returns? ;-)
Processors have been using longer bit widths - including 128 bits and longer - for calculations for ages. You find them in vector and SIMD extensions.
The key point about being a "64-bit architecture" is not the data width, but the address width. You need 64 bits to be able to sensibly use more than 4GB of memory. Since 64 bits is enough for 16 thousand million GB, it will be a while before you need more address bits in a single machine - even if you use some bits for address space randomisation.
There is also little call for normal integers bigger than 32-bit, never mind bigger than 64-bit. The hardware required to fully support these is out of proportion with their usefulness.
So while there will be steadily more support for longer data in vector and SIMD operations, don't expect pure 128-bit architectures to ever appear.
Since ARM is only designing IPs and if it is going to take two year to bring out the first prototype, it would be better it they plan for 128bit processing with 64bit compatibility. As all the processor manufacturers are having their 64bit variants in its place.
128 bit! Hmmmm, does that mean 128 bit encryption is at higher risk? Certainly chew through options quick!
Imagine running 64 bit programs at double data rate. We're smokin chips now! :-)
Any word on clock speeds?
I would suspect Windows 8,
seeing as how other OEMs are working with it. CE Compact may be an option, but maybe not optimal. But certainly not RISC structured right? ICBW, but not too often. I really appreciate the open architecture format better. Expensive biannual "too little, Too Late" upgrades, fraught with problems, just don't move me! The open software is exposing the world to some really creative minds and solutions for only pennies by comparison. And always several variants(competition)with unique or at least refined approaches.
I see a singular corporate hold on the development of programs and alternatives as destructive as the Dark Ages on creativity and advancement of the quality of life and success for mankind.
Doesn't mean I do not use them, just that I keep my options open, and my DROIDs handy.
I, for one, am pleased.
I currently have several ARM32 projects underway and no doubt will soon avail myself to the ARM64s as they are ready. So more MIPS is good if power demand is still admirably low.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.