Ignore:
Timestamp:
Jan 18, 2011, 3:45:34 PM (15 years ago)
Author:
[email protected]
Message:

2011-01-18 Geoffrey Garen <[email protected]>

Reviewed by Darin Adler.

Removed RegisterFile::markGlobals because it was obtuse, and it
unnecessarily relied on conservative marking.
https://bugs.webkit.org/show_bug.cgi?id=52668

  • interpreter/RegisterFile.h: Removed markGlobals.
  • runtime/JSActivation.cpp: (JSC::JSActivation::markChildren): Added a comment explaning why some JSActivations don't always mark their registers arrays.
  • runtime/JSGlobalObject.cpp: (JSC::JSGlobalObject::markChildren): Instead of calling markGlobals, mark the registers array directly.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/ChangeLog

    r76076 r76078  
     12011-01-18  Geoffrey Garen  <[email protected]>
     2
     3        Reviewed by Darin Adler.
     4
     5        Removed RegisterFile::markGlobals because it was obtuse, and it
     6        unnecessarily relied on conservative marking.
     7        https://bugs.webkit.org/show_bug.cgi?id=52668
     8
     9        * interpreter/RegisterFile.h: Removed markGlobals.
     10
     11        * runtime/JSActivation.cpp:
     12        (JSC::JSActivation::markChildren): Added a comment explaning why some
     13        JSActivations don't always mark their registers arrays.
     14
     15        * runtime/JSGlobalObject.cpp:
     16        (JSC::JSGlobalObject::markChildren): Instead of calling markGlobals, mark
     17        the registers array directly.
     18
    1192011-01-18  Michael Saboff  <[email protected]>
    220
Note: See TracChangeset for help on using the changeset viewer.