As long as the target of the execute is not in a D-bank cache line, you shouldn't see a big "hit" in processing cycles.
If it is, then it has to be flushed out, refetched to I-bank, pulled into the pipe, processed, flushed back out, and then back to D-bank (if still needed). This is based on my memory of the process when we first went to 256 byte cache lines w/ I/D bank caching. Sent from my iPhone > On Nov 23, 2016, at 4:57 AM, Philippe Cloarec <philippe.cloa...@gmail.com> > wrote: > > Hi Rob, > > ref:It's in the same cache line or it's not. > > Actually this was exactly my point and I was confused about seen various > coding approaches to reach that purpose to optimize > as much as possible CPU use. > > later > > Philippe
