First Principles of Interacting with Datapaths

Before we go into the anecdote, I need to state out the four rules. This is important, because it played a massive role in the next story. Well, I should rather call it a novel because this one has lasted over three test-cycles!

There are four principles on interacting with datapaths. To stay true to my nature as a computer component, I'm going to have to change the numbering and zero-index them - I'm sorry, but the "first rule" was pesking me! If you take offense to that, remember there is a zeroth law of thermodynamics!

Zeroth Rule: NEVER switch your registers for a datapath until you know, for sure, that THEY want to share a die with you.

First Rule: If switching registers, make sure to let out the data in those registers to avoid a registerbreak.

Second Rule: Just because a datapath is nice to you and offers to do something they/your branch predictor friends normally won't, it does not mean that they are into you. They're just being nice to you.

Third Rule: Don't judge a datapath based on how "pretty" they are (based on how that's defined). Instead, understand their componentality and see if they are your type, and if you can envision a billion cycles with them just based on componentality alone.