[armedbear-ticket] [armedbear] #33: Measure the impact of filling stack trace information when performing GO/RETURN/THROW

[armedbear]

#33: Measure the impact of filling stack trace information when performing
GO/RETURN/THROW
----------------------------------------------------------------------+-----
 Reporter:  vvoutilainen                                              |       Owner:  somebody   
     Type:  task                                                      |      Status:  new        
 Priority:  minor                                                     |   Milestone:  unscheduled
Component:  component1                                                |     Version:  1.0        
 Keywords:  exception ConditionThrowable go return throw performance  |  
----------------------------------------------------------------------+-----
 Douglas R. Miles reported recently that
 java.lang.Throwable.fillInStackTrace() can be a very time consuming
 operation when instantiating Throwables or objects the class of which
 extends Throwable.

 A patch for overriding the fillInStackTrace() function with an empty
 implementation was created, it seems to be a performance gain, but a
 benchmark is required. ANSI tests test so many other things that it's
 difficult to compare the impact of the patch without a test that tests
 only GO/RETURN/THROW.

-- 
Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/33>
armedbear <http://common-lisp.net/project/armedbear>
armedbear