On 2007-03-19, Timothy Normand Miller wrote: > I THINK I see what you're suggesting. Since the pipeline is totally > deterministic, we know at compile time exactly where a result is going > to be, so we could alias certain register numbers to refer to those > pipeline slots. > > However, if we ever want to allow interrupts or anything else that > would alter pipeline flow, we can't do this.
Thanks again for the clarification; I didn't consider that. We could save the memory-stage register twice as the first two instruction of any interrupt, but it seems impossible to restore the pipeline state without help from a return instruction. It's probably simpler to implement the short-cut paths. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
