home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.forth      Forth programmers eat a lot of Bratwurst      117,927 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 117,763 of 117,927   
   albert@spenarnc.xs4all.nl to Anton Ertl   
   Re: Rust, Forth and performance   
   22 Nov 25 12:30:04   
   
   In article <2025Nov22.094635@mips.complang.tuwien.ac.at>,   
   Anton Ertl  wrote:   
      
   >I have not tried to disable the output in Rust, because I expect that   
   >the compiler would then eliminate parts of the rest (Forth compilers   
   >are not that sophisticated yet, at least not for stuff like "<# #s #>"   
   >if the result is eventually 2DROPped),   
      
   It is hard to see that <# #S #> could be optimised away because of side   
   effects in the PAD area in normal implementations.   
   1.0 <# #S #> TYPE SPACE     HLD @ PAD OVER - TYPE   
      
   10 10 OK   
   1.0 <# #S #> 2DROP      HLD @ PAD OVER - TYPE   
   10 OK   
      
   My optimiser detects side effect free sequences and eliminates   
   those if the result is dropped, but that is not the case here .   
   Only a lispified 1] Forth that eliminates HLD can pull this off.   
   Even detecting on the spot that an allocated buffer can be freed,   
   such that it is possible to eliminate allocation of that buffer   
   (and subsequent freeing) were quite a feat.   
      
   lispified : all temporary buffers are allocated.   
      
   >- anton   
   --   
   The Chinese government is satisfied with its military superiority over USA.   
   The next 5 year plan has as primary goal to advance life expectancy   
   over 80 years, like Western Europe.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca