Instruction-fetch behaviour: undefined byte in 2-byte instructions
Posted: Thu Jul 06, 2023 4:46 pm
Hi,
Chapter 3.5.4.1 Little-Endian Fetch Semantics of the Xtensa Instruction Set Architecture (ISA) Summary [1] provides some example code on its behaviour. One of the comments states:
"-- now have a 24-bit instruction (8 bits undefined if 16-bit), break it into fields"
If I replace the op-code of a 2-byte instruction with the op-code of a 3-byte instruction, would the processor take the first byte of the next instruction as the third byte of the current (former 2-byte) instruction? (That is the behaviour that x86 processors would show in this situtation.)
[1] https://esp32.com/download/file.php?id=10134
Regards
Chapter 3.5.4.1 Little-Endian Fetch Semantics of the Xtensa Instruction Set Architecture (ISA) Summary [1] provides some example code on its behaviour. One of the comments states:
"-- now have a 24-bit instruction (8 bits undefined if 16-bit), break it into fields"
If I replace the op-code of a 2-byte instruction with the op-code of a 3-byte instruction, would the processor take the first byte of the next instruction as the third byte of the current (former 2-byte) instruction? (That is the behaviour that x86 processors would show in this situtation.)
[1] https://esp32.com/download/file.php?id=10134
Regards