I've been browsing over all the Propeller discussions, coming up to speed, and I'm a little confused by the terminology.
From my computing education and experience, the term "assembly code" used to describe human-readable text, like this:
entry·· mov··· t1,par
· ······· add···· t1,#4 << 2
··· ····· rdlong· t2,t1
····· ··· mov···· rxmask,#1
······· · shl··· ·· rxmask,t2
but what actually runs in the processor was referred to as "machine code" and appears like a list of 32 bit numbers, like this (made-up) example, shown here in hex; often described as the ones and zeroes that hardware understands:
With the simpler processors of the past, there was no confusion between the two because all processors ran only machine code.
But as we get into more sophisticated architectures like the Propeller, which can accept both SPIN byte-code tokens and assembly (machine code?), I want to verify my understanding.
Assembly, as conventionally referred to, isn't run in the Propeller, right? That text, entered in the IDE, is translated by the SPIN IDE, using something similar to SASM, into machine code, right?
But with so many people referring to the native Propeller code as assembly, I think I'd be swimming against the tide to insist on using the term "machine code".
So do we use the term "assembly" to refer to both what people can write in the IDE, as shown above, and its translation, formerly known as machine code, that runs in the Propeller?