Re: Avoid treating the stack as an array [Re: "Back & Forth" is back!]

anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:

@InProceedings{ertl22-locals,
 author =       {M. Anton Ertl},
 title =        {Are Locals Inevitably Slow?},
 crossref =     {euroforth22},
 pages =        {48--49},
 url =          {http://www.euroforth.org/ef22/papers/ertl-locals.pdf},
 url-slides =   {http://www.euroforth.org/ef22/papers/ertl-locals-slides.pdf},
 video =        {https://www.youtube.com/watch?v=tPjSKetEJn0},
 OPTnote =      {presentation slides},
 abstract =     {Code quality of locals on two code examples on
                 various systems}
}
>
An update on the table for the example:
>
: 3dup.3 {: a b c :} a b c a b c ;
>
  instr. bytes  system
   31    117    Gforth AMD64
   16     44    iforth 5.0.27 (plus 20 bytes entry and return code)
    7     19    lxf 1.6-982-823 32-bit
   32    127    SwiftForth 4.0.0-RC89 (calls LSPACE)
   26     92    VFX Forth 64 5.11 RC2

And here's another update.  A recent change in Gforth resulted in more
code, and we now have reverted that change:

   instr. bytes  system
    28    103    Gforth AMD64
    16     44    iforth 5.0.27 (plus 20 bytes entry and return code)
     7     19    lxf 1.6-982-823 32-bit
    32    127    SwiftForth 4.0.0-RC89 (calls LSPACE)
    26     92    VFX Forth 64 5.11 RC2

- anton
--
M. Anton Ertl  http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
     New standard: https://forth-standard.org/
   EuroForth 2024: https://euro.theforth.net