[bug #57741] Strange begin drop again ;

[Anton Ertl]

Update of bug #57741 (project gforth):

                  Status:                    None => Confirmed              
             Assigned to:                    None => anton                  

    _______________________________________________________

Follow-up Comment #1:

The gforth engine (without stack caching; for gforth-fast NIP would have the
same effect as DROP for gforth) does not try to access the stack when
DROPping.  In the usual case the stack underflow is discovered in the first
word afterwards that accesses memory (e.g., because it actually does something
with the stack item, or because it tries to push something), which is usually
pretty soon.  Your example is one of the rare cases where this does not
happen.  We could fix this by adding a memory access in DROP (and some other
words), but I am not sure if this is worth the effort and the slowdown.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57741>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/