1. 13 Dec, 2019 1 commit
  2. 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
  3. 20 Sep, 2018 1 commit
  4. 02 Jul, 2018 1 commit
  5. 02 Feb, 2018 1 commit
  6. 30 Nov, 2017 1 commit
  7. 31 Jul, 2017 1 commit
  8. 28 Jul, 2017 4 commits
  9. 28 Jun, 2017 1 commit
  10. 27 Mar, 2017 1 commit
  11. 30 Nov, 2016 1 commit
    • clemensh's avatar
      [wasm] Remove raw byte pointers from WasmModule · 6572b562
      clemensh authored
      These byte pointers (module_start and module_end) were only valid
      during decoding. During instantiation or execution, they can get
      invalidated by garbage collection.
      This CL removes them from the WasmModule struct, and introduces a new
      ModuleStorage struct as interface to the wasm wire bytes.
      Since the storage is often needed together with the ModuleEnv, a new
      ModuleStorageEnv struct holds both a ModuleEnv and a ModuleStorage.
      The pointers in the ModuleStorage should never escape the live range of
      this struct, as they might point into a SeqOneByteString or ArrayBuffer.
      Therefore, the WasmInterpreter needs to create its own copy of the
      whole module.
      Runtime functions that previously used the raw pointers in WasmModule
      (leading to memory errors) now have to use the SeqOneByteString in the
      WasmCompiledModule.
      
      R=titzer@chromium.org
      BUG=chromium:669518
      
      Review-Url: https://codereview.chromium.org/2540133002
      Cr-Commit-Position: refs/heads/master@{#41388}
      6572b562
  12. 20 Sep, 2016 1 commit
  13. 25 Aug, 2016 1 commit
  14. 27 Nov, 2015 1 commit
  15. 11 Jun, 2015 1 commit
  16. 22 Apr, 2015 3 commits
  17. 31 Jan, 2015 1 commit
  18. 08 Jan, 2015 1 commit
  19. 02 Dec, 2014 1 commit
  20. 17 Nov, 2014 1 commit
  21. 14 Nov, 2014 2 commits
  22. 13 Nov, 2014 2 commits
  23. 14 Oct, 2014 1 commit
  24. 27 Aug, 2014 1 commit
  25. 26 Aug, 2014 1 commit
  26. 30 Jul, 2014 1 commit
  27. 20 Jun, 2014 1 commit
  28. 03 Jun, 2014 1 commit
  29. 29 Apr, 2014 1 commit
  30. 07 Feb, 2014 1 commit
  31. 11 Jul, 2013 1 commit
  32. 09 Jul, 2013 1 commit
  33. 24 May, 2013 1 commit