[IronJack]

a pipelined execution queue.

I'm not sure what you mean by that. But whatever the code is, it ultimately becomes machine language. I've always wondered why the executable wasn't written in the language the machine speaks to begin with.

[Myrddin]

A pipelined execution queue works like an automobile assembly line. The bus unit fetches instructions from memory and does some preliminary decoding. As the clock cycles progress, necessary elements are pulled from memory and filled in. Finally, the finished elements are ready for the CPU proper to execute a logic instruction, addition load/store, etc. Successful operation of this queue is dependent on proper assembly and sequencing. If you goof, everything behind the "goof" point is scrapped, the "assembly line" is flushed and a new series of bus fetches begins. A long "stall" occurs at the CPU end of the line because the "assembly line" is being rebuilt. A "jump" or branch to a new address beyond the internal queue of instructions makes it necessary to restart.