1. 06 Feb, 2020 1 commit
    • Tobias Tebbi's avatar
      [profiler] fix 4 bugs in --prof/linux-tick-processor · 58b45cca
      Tobias Tebbi authored
      - In log.cc, we used InstructionStart() for code create events, but
        the Code object address for code move events. Change to use
        InstructionStart() for both.
      - The symbol table contains some kind of virtual address, not file
        offsets. They happened to be identical in the past but are no longer,
        probably due to toolchain changes. Now we use objdump to figure out
        the difference between virtual addresses and file offsets.
      - When a new code object happened to be created at the same address as
        a previous one, we wouldn't update it.
        This is indeed wrong, as predicted in a TODO by Jaro.
      - For 64bit addresses, using >>> is wrong, now replaced with division.
      
      
      Change-Id: Ib23114ed736f98bfc33c65004a039a3fd04d3c49
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2016586Reviewed-by: 's avatarMichael Stanton <mvstanton@chromium.org>
      Commit-Queue: Tobias Tebbi <tebbi@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#66145}
      58b45cca
  2. 28 May, 2019 1 commit
  3. 31 Oct, 2018 1 commit
  4. 29 Oct, 2018 1 commit
  5. 24 Oct, 2018 1 commit
  6. 11 Apr, 2017 1 commit
  7. 04 Mar, 2017 1 commit
  8. 10 Jun, 2016 1 commit
  9. 05 Apr, 2016 1 commit
  10. 03 Sep, 2015 1 commit
  11. 05 May, 2015 1 commit
  12. 20 Jan, 2015 1 commit
    • jkummerow's avatar
      Profiler improvements · feffccca
      jkummerow authored
      (1) --prof-cpp: Collects ticks like --prof, but ignores code creation events to reduce distortion (so all JS ticks will be "unaccounted"). Useful for profiling C++ code.
      (2) --timed-range flag for tick processor: Ignores ticks before the first and after the last call to Date.now(). Useful for focusing on the timed section of a test.
      
      Review URL: https://codereview.chromium.org/802333002
      
      Cr-Commit-Position: refs/heads/master@{#26168}
      feffccca
  13. 23 Aug, 2013 1 commit
  14. 29 Jan, 2013 1 commit
  15. 16 Jul, 2012 1 commit
  16. 13 Feb, 2012 1 commit
  17. 18 Jan, 2010 1 commit
    • mikhail.naganov@gmail.com's avatar
      Fix issue 571: display descriptive names for code objects from snapshot. · 37d39724
      mikhail.naganov@gmail.com authored
      As this is only needed for internal profiling (not for DevTools),
      the following approach had been chosen:
      
       - during snapshot creation, positions of serialized objects inside
         a snapshot are logged;
      
       - then during V8 initialization, positions of deserealized objects
         are logged;
      
       - those positions are used for retrieving code objects names from
         snapshot creation log, which needs to be supplied to tick processor
         script.
      
      Positions logging is controlled with the new flag: --log_snapshot_positions.
      This flag is turned off by default, and this adds no startup penalty.
      
      To plug this fix to Golem, the following actions are needed:
      
       - logs created using 'mksnapshot' need to be stored along with VM images;
      
       - tick processor script needs to be run with '--snapshot-log=...' cmdline
         argument.
      
      BUG=571
      
      Review URL: http://codereview.chromium.org/551062
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3635 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      37d39724
  18. 14 Jul, 2009 1 commit
  19. 09 Jul, 2009 1 commit
  20. 27 Feb, 2009 1 commit
  21. 16 Jan, 2009 1 commit
  22. 14 Jan, 2009 1 commit
  23. 26 Sep, 2008 1 commit
  24. 09 Sep, 2008 1 commit
  25. 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
  26. 03 Jul, 2008 1 commit