From: quadibloc@invalid.invalid   
      
   On Sat, 20 Dec 2025 20:15:51 +0000, MitchAlsup wrote:   
      
   > For argument setup (calling side) one needs MOV   
   > {R1..R5},{Rm,Rn,Rj,Rk,Rl}   
   > For returning values (calling side)   needs MOV {Rm,Rn,Rj},{R1..R3}   
   >   
   > For loop iterations                   needs MOV {Rm,Rn,Rj},{Ra,Rb,Rc}   
   >   
   > I just can't see how to make these run reasonably fast within the   
   > constraints of the GBOoO Data Path.   
      
   Since you actually worked at AMD, presumably you know why I'm mistaken   
   here...   
      
   when I read this, I thought that there was a standard technique for doing   
   stuff like that in a GBOoO machine. Just break down all the fancy   
   instructions into RISC-style pseudo-ops. But apparently, since you would   
   know all about that, there must be a reason why it doesn't apply in these   
   cases.   
      
   John Savard   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)