1. 17 Nov, 2014 1 commit
    • dslomov's avatar
      harmony-scoping: Implement debugger support for script scope. · d7e3697d
      dslomov authored
      We add a new ScopeType, ScopeType.Script. The scope with
      ScopeType.Script is always present in the scope chain (ScopeIterator
      fakes it if neededi - i.e. if ScriptContext for a script has not been
      allocated since that script has no lexical declarations).
      ScriptScope reflects ScriptContextTable.
      
      R=yurys@chromium.org,yangguo@chromium.org
      BUG=v8:3690
      LOG=N
      
      Review URL: https://codereview.chromium.org/726643002
      
      Cr-Commit-Position: refs/heads/master@{#25383}
      d7e3697d
  2. 04 Jun, 2013 1 commit
  3. 10 Aug, 2012 1 commit
  4. 26 Apr, 2012 2 commits
  5. 28 Feb, 2012 1 commit
  6. 24 Jan, 2012 2 commits
  7. 04 Jan, 2012 1 commit
  8. 13 Jul, 2011 1 commit
  9. 08 Jul, 2011 1 commit
  10. 07 Jul, 2011 1 commit
  11. 06 Jul, 2011 1 commit
  12. 29 Jun, 2011 1 commit
    • sgjesse@chromium.org's avatar
      Support debugger inspection of locals in optimized frames · 7d2be7c0
      sgjesse@chromium.org authored
      Optimized frames are now handled by the debugger. When discovering optimized frames during stack inspection in the debugger they are "deoptimized" using the normal deoptimization code and the deoptimizer output information is used to provide frame information to the debugger.
      
      Before this change the debugger reported each optimized frame as one frame no matter the number of inlined functuions that might have been called inside of it. Also all locals where reported as undefined. Locals can still be reposted as undefined when their value is not "known" by the optimized frame.
      
      As the structures used to calculate the output frames when deoptimizing are not GC safe the information for the debugger is copied to another structure (DeoptimizedFrameInfo) which is registered with the global deoptimizer data and processed during GC.
      
      R=fschneider@chromium.org
      
      BUG=v8:1140
      TEST=test/mjsunit/debug-evaluate-locals-optimized*
      
      Review URL: http://codereview.chromium.org//7230045
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8464 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      7d2be7c0
  13. 03 Feb, 2009 1 commit
  14. 09 Sep, 2008 1 commit
  15. 22 Aug, 2008 1 commit
    • christian.plesner.hansen's avatar
      Included mjsunit JavaScript test suite and C++ unit tests. · c42f5829
      christian.plesner.hansen authored
      In the shell sample don't print the result of executing a script, only
      evaluating expressions.
      
      Fixed issue when building samples on Windows using a shared V8
      library.  Added visibility option on Linux build which makes the
      generated library 18% smaller.
      
      Changed build system to accept multiple build modes in one build and
      generate seperate objects, libraries and executables for each mode.
      
      Removed deferred negation optimization (a * -b => -(a * b)) since this
      visibly changes operand conversion order.
      
      Improved parsing performance by introducing stack guard in preparsing.
      Without a stack guard preparsing always bails out with stack overflow.
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c42f5829