History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRUBY-1603
Type: Bug Bug
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Minor Minor
Assignee: Charles Oliver Nutter
Reporter: Charles Oliver Nutter
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JRuby

Boxed variable compilation could use lighter-weight scopes

Created: 21/Nov/07 10:16 PM   Updated: 07/Oct/08 12:01 AM
Component/s: Compiler
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified


 Description  « Hide
When a scope contains no boxed variables, but the boxed variable compiler is being used, it may be a perf win to use a lighter-weight scope than DynamicScope. DynamicScope is already lazily allocating the variable array it contains, but it could be made lighter by eliminating all references used for variable management. This could make some method bodies with no captures variables faster to execute, since they'd have less per-call overhead.

Also, as part of this fix, boxed variable scopes with no captured variables could skip the initialize-all-vars-to-nil for the DynamicScope they're using. This would eliminate that init cost for those methods.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Charles Oliver Nutter - 15/Feb/08 12:55 PM
Removing target release from issues that fit any of the following criteria:
  • No known way to fix them
  • Java integration enhancements out of scope for 1.1 release
  • Other out of scope issues for 1.1

Charles Oliver Nutter - 07/Oct/08 12:01 AM
With block-as-binding now again in play for 1.9 it doesn't look like there's any chance of optimizing local variables in a "boxed" variable scope. I'm marking this WONTFIX. We may get to revisit this some day when things change in the Ruby world, but it's not likely.