What is certainly true is that a single instruction could do a lot, making for much more concise code than would be the case for RISC code.
IBM S/360 is probably the most influential CISC architecture. There is lots of S/360 documentation online. If of interest I did a short post on S/360 assembly a little while ago.
https://thechipletter.substack.com/p/writing-ibm-s360-assemb...
I genuinely had no idea how awful it was - of course you don't see pop-ups if you are logged in. To be fair to Substack the control to turn off pop-ups was there but it was turned on by default and a bit buried away in the UI.
I've removed any mid-article calls to action and turned off pop-ups now so hopefully a much better and less aggressive experience.
On the S/360, the article I linked too was a short look at how complex some S/360 instructions were and at how assembly used to be written using pen and paper. If you're interested in more on S/360 Assembly then the principles of operation may be worth a scroll through.
Thanks again - really appreciate that you fed back rather than just closing your browser window.
[1] http://bitsavers.org/pdf/ibm/360/princOps/A22-6821-0_360Prin...
Interesting. Was the guiding principle of CISC ISAs essentially that be easy to write assembly code for then? Maybe it's obvious but I had never considered how or where CISC evolved from. Would I have to look at something like the history of the VAX ISA to understand this better?