Click here to Skip to main content
15,887,175 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
GeneralRe: Emmanuel Katto Uganda | How can I learn Java? Pin
Cp-Coder28-Oct-23 2:14
Cp-Coder28-Oct-23 2:14 
GeneralCCC 2023-10-27 Pin
Peter_in_278026-Oct-23 22:08
professionalPeter_in_278026-Oct-23 22:08 
GeneralRe: CCC 2023-10-27 Pin
pkfox26-Oct-23 22:38
professionalpkfox26-Oct-23 22:38 
GeneralRe: CCC 2023-10-27 - winner! Pin
Peter_in_278026-Oct-23 22:45
professionalPeter_in_278026-Oct-23 22:45 
JokeRe: CCC 2023-10-27 Pin
englebart27-Oct-23 5:32
professionalenglebart27-Oct-23 5:32 
GeneralA future without x86? Pin
honey the codewitch26-Oct-23 21:48
mvahoney the codewitch26-Oct-23 21:48 
GeneralRe: A future without x86? Pin
Ron Anders27-Oct-23 3:30
Ron Anders27-Oct-23 3:30 
GeneralRe: A future without x86? Pin
trønderen27-Oct-23 5:17
trønderen27-Oct-23 5:17 
I have been fighting x86 since 1992-93, but lost the first battle: The IT department of the Tech. College where I was teaching had two alternatives for a set of 30 new machines, to be used for Unix software and also one of my courses, Computer Architecture (with assembler coding). The choice was made in a democratic manner: The educational staff of the department, including me, came out in favor of an M68030 based system. The department head was in favor of the x86 based solution. When he saw that the majority went against his preference, he announced: I can't be the head of a department that works against me. I quit! Find another department head! So the next day, we repeated the democratic voting, and this time the majority was in favor of the department head's preference, and he didn't quit. I had to teach Introduction to Computer Architecture on the messiest architecture around.

(Btw, Denmark got into EU by a similar democratic vote. They had a referendum, giving an 'no' to join EU. The Danish authorities told the people that the answer was wrong, and gave the people another chance to give the right answer. The second time, The People understood what was expected of them, and Denmark joined EU. Hooray for democratic processes! At least as long as they give The Right Answer.)

M68K didn't survive in the big markets. If it had, the RISC wave would have been mostly superfluous. So let's cross our fingers that the ARM architecture will be strong enough to fight down the x86/x64.

Although ARM started as a 'clean' RISC, it certainly isn't any more today! The very first 'Thumb' instruction set laid the first ground for irregular instruction coding, need for an intermediate decoding level and reduced regularity of the instruction set. That has grown 'worser and worser' with every new architecture revision; it is today very far from the RISC ideal of instruction word bits directly activating the various logic circuits. They have had to introduce caching and pipelining and lookahead and speculative execution and out-of-order execution and whathaveuyou of hardware speedup techniques. The instruction set has grown and grown and grown and ... Certainly not always in an orderly, well designed manner. AArch hasn't had as many years as x86/64 to grow cancer, but the old word saying that 'any sufficiently high-versioned standard is indistinguishable from a can of worms' is beginning to bite ARM as well.

Note that the discussion you are referring to is more than three years old. The thread is almost void of references to the Aarch64 alternatives that were available even then, but with plenty of references to the M1 of 2007. It it tempting to suspect that a fair share of the commenters are not fully aware of the more recent (even then) updates to the architecture.

If you go for the detail, 'the ARM Cortex architecture is largely continuous from their little M0 real time chips all the way up to their multicore A line' does hold true for a sizable core. Not for the Thumb instruction sets. A number of the 'ordinary' instructions didn't make it to the 64 bit architecture. Compatibility at the binary level is significantly less than at the assembler source code level; some of the top Aarch64 models have completely dropped support for Aarch32. Vector instructions are now in its second version of the second generation.

Yet: I do like the general ARM architecture. I have come to love the register based philosophy, with less reliance on the stack. I have seen how the system architecture for 'peripherals' integral to the CPU is great for extending the CPU in a SoC. I am really hoping that traditional PC manufacturer soon will come up with a broader range of ARM based machines, covering even the more 'classical' kind of desktop machines in large cabinets, allowing for extensions with peripherals, memory etc. that you can't do with a portable or tablet.

'The fact that ARM doesn't manufacture is also a huge win' - it is, but don't overestimate it. ARM provides a CPU core, for anyone else to extend with their own (on-chip) peripherals, several architectural features are optional, and every manufacturer will pack the chip to his preferences. So you will rarely if ever see a 'plugin compatible' chip from an alternate vendor. If you have to switch to another chip manufacturer, be prepared for another pin layout, maybe your old chip had some useful peripherals missing in the new one (and if the new one has some similar peripheral, it is almost certainly managed differently) and some instruction codes may be invalid because that option was left out of your new replacement chip.

A common core is of course a great win. But the salesman speak is often a lot more rosy than realities, especially if you are making use of optional functions and on-chip peripherals.
GeneralRe: A future without x86? Pin
englebart27-Oct-23 5:40
professionalenglebart27-Oct-23 5:40 
GeneralRe: A future without x86? Pin
k505427-Oct-23 7:57
mvek505427-Oct-23 7:57 
GeneralRe: A future without x86? Pin
honey the codewitch27-Oct-23 9:08
mvahoney the codewitch27-Oct-23 9:08 
GeneralRe: A future without x86? Pin
trønderen28-Oct-23 7:05
trønderen28-Oct-23 7:05 
GeneralRe: A future without x86? Pin
Richard Andrew x6427-Oct-23 14:34
professionalRichard Andrew x6427-Oct-23 14:34 
GeneralRe: A future without x86? Pin
honey the codewitch27-Oct-23 22:33
mvahoney the codewitch27-Oct-23 22:33 
GeneralRe: A future without x86? Pin
Member 1330167930-Oct-23 2:36
Member 1330167930-Oct-23 2:36 
GeneralRe: A future without x86? Pin
honey the codewitch30-Oct-23 4:51
mvahoney the codewitch30-Oct-23 4:51 
GeneralRe: A future without x86? Pin
Peter Adam29-Oct-23 22:53
professionalPeter Adam29-Oct-23 22:53 
GeneralRe: A future without x86? Pin
honey the codewitch30-Oct-23 4:53
mvahoney the codewitch30-Oct-23 4:53 
GeneralRe: A future without x86? Pin
jschell30-Oct-23 6:11
jschell30-Oct-23 6:11 
GeneralRe: A future without x86? Pin
honey the codewitch30-Oct-23 7:40
mvahoney the codewitch30-Oct-23 7:40 
GeneralRe: A future without x86? Pin
Peter Adam30-Oct-23 6:17
professionalPeter Adam30-Oct-23 6:17 
GeneralRe: A future without x86? Pin
honey the codewitch30-Oct-23 12:38
mvahoney the codewitch30-Oct-23 12:38 
GeneralRe: A future without x86? Pin
obermd30-Oct-23 3:52
obermd30-Oct-23 3:52 
GeneralRe: A future without x86? Pin
Member 1419238230-Oct-23 5:34
Member 1419238230-Oct-23 5:34 
GeneralRe: A future without x86? Pin
sasadler30-Oct-23 6:33
sasadler30-Oct-23 6:33 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.