1. 17 Oct, 2019 1 commit
    • Zhou, Zhiguo's avatar
      Log debug info of WASM for Intel VTune Amplifier · ec580709
      Zhou, Zhiguo authored
      This CL logs debug information of WASM in Intel VTune Amplifer via
      VTune's JIT Profiling API. With this CL, the profiling information
      of JITted code and its corresponding C/C++ source code is displayed
      optionally. To use this feature, a runtime flag "vtune_prof_annotat
      e_wasm" should be passed to the VTune-enabled V8 engine. Currently,
      the inline function in C/C++ is not well supported due to the
      limitation of source map.
      
      As a drive-by fix, the dynamically allocated event-specific data
      of JavaScript (src/third_party/vtune/vtune-jit.cc) is managed with
      C++ containers for safety.
      
      Change-Id: Ic27420fcdcd775bc5c7778abf5cff6edf0fb38b6
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1782126Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Reviewed-by: 's avatarToon Verwaest <verwaest@chromium.org>
      Commit-Queue: Zhiguo Zhou <zhiguo.zhou@intel.com>
      Cr-Commit-Position: refs/heads/master@{#64351}
      ec580709
  2. 12 Aug, 2019 1 commit
  3. 31 May, 2019 1 commit
  4. 27 May, 2019 1 commit
    • Clemens Hammacher's avatar
      [cleanup] Replace simple typedefs by using · a335f2ae
      Clemens Hammacher authored
      This replaces all typedefs that define types and not functions by the
      equivalent "using" declaration.
      
      This was done mostly automatically using this command:
      ag -l '\btypedef\b' src test | xargs -L1 \
           perl -i -p0e 's/typedef ([^*;{}]+) (\w+);/using \2 = \1;/sg'
      
      Patchset 2 then adds some manual changes for typedefs for pointer types,
      where the regular expression did not match.
      
      R=mstarzinger@chromium.org
      TBR=yangguo@chromium.org, jarin@chromium.org
      
      Bug: v8:9183
      Change-Id: I6f6ee28d1793b7ac34a58f980b94babc21874b78
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1631409
      Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
      Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#61849}
      a335f2ae
  5. 24 Apr, 2019 1 commit
  6. 23 Jul, 2018 1 commit
  7. 16 Jul, 2018 1 commit
  8. 28 Mar, 2018 1 commit
  9. 23 Jan, 2018 1 commit
  10. 02 Aug, 2017 1 commit
  11. 13 Feb, 2017 1 commit
  12. 02 May, 2016 1 commit
  13. 30 Apr, 2016 2 commits
  14. 29 Apr, 2016 1 commit
  15. 25 Apr, 2016 1 commit
    • machenbach's avatar
      [build] Prepare moving v8.gyp to src/ · cb855fe7
      machenbach authored
      This will allow to pull in gyp as a deps to the same location
      as chromium (tools/gyp not build/gyp), needed for gn switch.
      
      This is the first step of a 3-way move.
      1) Copy v8.gyp in v8
      2) Update references in embedders (follow up)
      3) Remove old v8.gyp (follow up)
      
      BUG=chromium:474921
      LOG=n
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1920793002
      
      Cr-Commit-Position: refs/heads/master@{#35760}
      cb855fe7
  16. 09 Dec, 2015 1 commit
  17. 20 Jul, 2015 1 commit
  18. 16 Jun, 2015 1 commit
  19. 22 Oct, 2014 1 commit
    • jochen@chromium.org's avatar
      Update intialization of vtune support. · 7a70d6a0
      jochen@chromium.org authored
       In R23940 (https://code.google.com/p/v8/source/detail?r=23940) it introduces
       Isolate::CreateParams and mentions that V8::SetJitCodeEventHandler should either
       be passed to Isolate::New as well, or invoked via the Isolate.
      
       When Chrome as embedder of V8, we will set the Jit Code event handler for Vtune
       support during the initialization of renderer process and V8 has be initialized
       at that time. It's better that we invoke V8::SetJitCodeEventHander via the Isolate.
       So we change the vTune::InitializeVtuneForV8(v8::Isolate::CreateParams& params) to
       vTune::InitializeVtuneForV8(v8::Isolate* isolate).
      
       we will do corresponding changes in chromium code if this patch is landed and Chromium
       updates V8 to the
       new release branch.
      
       some part of this patch is provided by denis.pravdin@intel.com.
      
      BUG=
      R=danno@chromium.org, jochen@chromium.org
      
      Review URL: https://codereview.chromium.org/655183002
      
      Patch from Chunyang Dai <chunyang.dai@intel.com>.
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@24811 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      7a70d6a0
  20. 15 Sep, 2014 1 commit
    • jochen@chromium.org's avatar
      Currently, a new isolate is created in an uninitialized state, and · 65a18578
      jochen@chromium.org authored
      several API methods will automatically initialize it. During this
      uninitialized state, code event handlers and function entry handlers can
      be attached to the isolate.
      
      This CL deprecates SetFunctionEntryHook and moves the configuration of
      those handlers to the Isolate factory method.
      
      This will allow for initializing the Isolate at creation time in the
      future.
      
      Users of V8::SetFunctionEntryHook should pass the entry hook to
      Isolate::New instead. V8::SetJitCodeEventHandler should either be passed
      to Isolate::New as well, or (if startup events are not required) invoked
      via the Isolate.
      
      BUG=none
      LOG=y
      R=svenpanne@chromium.org
      
      Review URL: https://codereview.chromium.org/570993002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23940 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      65a18578
  21. 15 Jul, 2014 1 commit
  22. 25 Apr, 2014 1 commit
  23. 16 Jan, 2014 5 commits
  24. 30 Jul, 2013 1 commit
  25. 10 Jul, 2013 1 commit
  26. 28 Jun, 2013 1 commit
  27. 24 Jun, 2013 1 commit
  28. 08 May, 2013 1 commit
  29. 07 May, 2013 1 commit
  30. 12 Apr, 2013 1 commit