From: quadibloc@invalid.invalid   
      
   On Sun, 21 Dec 2025 20:32:44 +0000, MitchAlsup wrote:   
   >> On Thu, 18 Dec 2025 21:29:00 +0000, MitchAlsup wrote:   
      
   >> > Or in other words, if you can decode K-instructions per cycle, you'd   
   >> > better be able to execute K-instructions per cycle--or you have a   
   >> > serious blockage in your pipeline.   
      
   > Not a typo--the part of the pipeline which is  narrowest is   
   > the part that limits performance. I suggest strongly that you should not   
   > make/allow the decoder to play that part.   
      
   I agree - and strongly, too - that the decoder ought not to be the part   
   that limits performance.   
      
   But what I quoted says that the execution unit ought not to be the part   
   that limits performance, with the implication that it's OK if the decoder   
   does instead. That's why I said it must be a typo.   
      
   So I think you need to look a second time at what you wrote; it's natural   
   for people to see what they expect to see, and so I think you looked at   
   it, and didn't see the typo that was there.   
      
   John Savard   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)