I must apologise if I periodically raise the same subjects as before, such as the graphics processor and instruction encodings, etc, but the situation is that I have a number of very deep seated interests other than just low-level computing, particularly amateur radio, horology, model railways and bellringing, and I tend to be single mindedly being utterly fascinated by only ever one at any time with the result that it can be many weeks or months before returning to any one interest.
However, it remains that my computing interest, resulting from my first real job 45 years ago, is to produce an interactive programming language (the interactivity of BASIC or FORTH) but that runs at the speed of compiled code and yet is fully reconstructable as the original source.
For example, due to operator precedence, parentheses might prove to be unnecessary, but you'd be justifiably miffed if they disappeared from the source code, as source code has human understandabilty considerations, and so it becomes necessary to insert a special form of NOP in the compiled code to represent the parentheses; only one NOP for each pair.
So, the reason for wanting the instruction encoding of the A53 (now discovered in excelsis) is to seek ambiguous forms of the same instruction to let me effectively insert such NOPs but without unnecessarily slowing down a program.
This interest might well be obsolete nowadays, now that there is no shortage of either RAM or disk files to store both source and object, but old habits die hard!
I also have no doubt that these ideas of mine will have been well resolved by countless others over the decades and that I will be re-inventing the wheel but calling it fire.
I previously worked on this project prior to retirement32 years ago with the CRAP and SOAS lanuages on the x86 processors but found that intensive programming in the evenings after intensive programming during the working hours was just too tiring.
CRAP, Create Rapidly Application Programs, was a tokenised interpreter, just to get the ideas down (just 6 weeks of eveinings and weekends to get an interpreter that could list itself) and SOAS, Shit Off A Shovel, was the faster version where the source code tokens were the compiled code itself.
Sorry, apologies again, waffling on!