1. 20 Sep, 2010 1 commit
    • mikhail.naganov@gmail.com's avatar
      Show RegExp calls in the profile. · c1903ce3
      mikhail.naganov@gmail.com authored
      It turns out they were filtered out. But when I unfiltered them, I
      discovered another issue: when DevTools run, regexp literals get
      recompiled each time they called (looks like this is concerned with
      switching to full compiler), so I ended up having multiple entries for
      the same regexp. To fix this, I changed the way of how code entries
      equivalence is considered.
      
      BUG=crbug/55999
      TEST=cctest/test-profile-generator/ProfileNodeFindOrAddChildForSameFunction
      (the test isn't for the whole issue, but rather for equivalence testing)
      
      Review URL: http://codereview.chromium.org/3426008
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5492 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c1903ce3
  2. 22 May, 2010 1 commit
  3. 18 May, 2010 1 commit
    • mikhail.naganov@gmail.com's avatar
      CPU profiler: add secure profiles by filtering out functions using security tokens. · 3d7ce8ac
      mikhail.naganov@gmail.com authored
      As several pages can run in a single V8 instance, it is possible to
      have functions from different security contexts intermixed in a single
      CPU profile.  To avoid exposing function names from one page to
      another, filtering is introduced.
      
      The basic idea is that instead of capturing return addresses from
      stack, we're now capturing JSFunction addresses (as we anyway work
      only with JS stack frames.)  Each JSFunction can reach out for
      context's security token. When providing a profile to a page, the
      profile is filtered using the security token of caller page. Any
      functions with different security tokens are filtered out (yes, we
      only do fast path check for now) and their ticks are attributed to
      their parents.
      
      Review URL: http://codereview.chromium.org/2083005
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4673 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      3d7ce8ac
  4. 15 Apr, 2010 1 commit
  5. 14 Apr, 2010 1 commit
  6. 12 Apr, 2010 1 commit
  7. 07 Apr, 2010 1 commit
  8. 06 Apr, 2010 1 commit
  9. 30 Mar, 2010 1 commit
  10. 19 Mar, 2010 1 commit
  11. 11 Mar, 2010 1 commit
  12. 04 Feb, 2010 1 commit
  13. 21 Dec, 2009 1 commit
  14. 27 Aug, 2009 2 commits
  15. 15 Jun, 2009 1 commit
  16. 05 Jun, 2009 1 commit
    • kmillikin@chromium.org's avatar
      Simplify the processing of deferred code in the code generator. Our · bd82b972
      kmillikin@chromium.org authored
      deferred code snippets are highly stylized.  They always make a call
      to a stub or the runtime and then return.  This change takes advantage
      of that.
      
      Creating a deferred code object now captures a snapshot of the
      registers in the virtual frame.  The registers are automatically saved
      on entry to the deferred code and restored on exit.
      
      The clients of deferred code must ensure that there is no change to
      the registers in the virtual frame (eg, by allocating which can cause
      spilling) or to the stack pointer.  That is currently the case.
      
      As a separate change, I will add either code to verify this constraint
      or else code to forbid any frame effect.
      
      The deferred code itself does not use the virtual frame or register
      allocator (or even the code generator).  It is raw macro assembler
      code.
      Review URL: http://codereview.chromium.org/118226
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2112 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      bd82b972
  17. 27 May, 2009 1 commit
  18. 31 Mar, 2009 3 commits
  19. 27 Mar, 2009 1 commit
  20. 16 Jan, 2009 1 commit
  21. 14 Jan, 2009 1 commit
  22. 26 Sep, 2008 1 commit
  23. 09 Sep, 2008 1 commit
  24. 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
  25. 03 Jul, 2008 1 commit