Last time I did that was on MSP430, where it seems that some integrated peripherals set completion interrupt flag one cycle before the operation really completes. (I'm not sure whether it really is bug, I didn't find this documented anywhere, but for TI's example this does not matter and produces marginally better performance)
> Include at least one instruction between the clear of an interrupt enable or interrupt flag and the EINT instruction. For example: Insert a NOP instruction in front of the EINT instruction.
> Include at least one instruction between DINT and the start of an code sequence that requires protection from interrupts. For example: Insert a NOP instruction after the DINT
Luckily if you use the MSP compiler's intrinsic functions to enable/disable interrupts it takes care of this for you.
True of certain x86 bugs too:
https://blogs.msdn.microsoft.com/oldnewthing/20110112-00/?p=...
https://en.wikipedia.org/wiki/Bubble_(computing)
https://en.wikipedia.org/wiki/Classic_RISC_pipeline#Hazards
More under-appreciated classic RISC trivia:
The MIPS is bi-endian, and it's referred to as SPIM when driving backwards.
For some reason, Sun never got around to making a bi-endian version of SPARC called CRAPS.
A similar trick can be found in this interesting article:
http://www.reenigne.org/blog/8088-pc-speaker-mod-player-how-...
This means that the 8088 will execute the unpatched version of the instruction (as it's already in the prefetch queue by the time it's patched).