From: tkoenig@netcologne.de   
      
   Stefan Monnier schrieb:   
   >>> Well, Mitch claims average 35 bits per instructions, that means about   
   >>> 90% utilization of decoders, so not bad.   
   >> His minimum instruction size is 32 bits, but I was going for 16 bits.   
   >   
   > BTW, my understanding of Mitch's design is that this is related to   
   > instruction complexity: if you support 16bit instructions, it means you   
   > support instructions which presumably don't do very much work because   
   > it's hard to express a lot of "work to do" in 16bit.   
      
   A bit of statistics on that.   
      
   Using a primitive Perl script to catch occurences, on a recent   
   My 66000 cmopiler, of the shape   
      
    [op] Ra,Ra,Rb   
    [op] Ra,Rb,Ra   
    [op] Ra,#n,Ra   
    [op] Ra,Ra,#n   
    [op] Ra,Rb   
      
   where |n| < 32, which could be a reasonable approximation of a   
   compressed instruction set, yields 14.9% (Perl), 16.6% (gnuplot)   
   and 23.9% (GSL) of such instructions. Potential space savings   
   would be a bit less than half that.   
      
   Better compression schemes are certainly possible, but I think the   
   disadvantages of having more complex encodings outweigh any   
   potential savings in instruction size.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|